All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #01; Tue, 05)
Date: Wed, 6 Aug 2008 07:21:28 -0700	[thread overview]
Message-ID: <20080806142128.GA28231@spearce.org> (raw)
In-Reply-To: <7vmyjqsm04.fsf@gitster.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> wrote:
> [New Topics]
> * sp/smart-http (Sun Aug 3 00:25:17 2008 -0700) 2 commits
>  - [do not merge -- original version] Add Git-aware CGI for Git-aware
>    smart HTTP transport
>  - Add backdoor options to receive-pack for use in Git-aware CGI
> 
> The "magic" detection protocol was revised to use POST to info/refs; the
> top one queued is from before that discussion.

I'm surprised you queued these.  They really are not ready for
application to a tree.  For example the CGI is really messed up for
trying to do Transfer-Encoding: chunked on its own, JH was right and
Apache does it for us.  That removed a good chunk of code from it.

Writing the client for this is slightly non-trivial.  I more-or-less
want to shove it into send-pack, not http-push, as the bulk of the
protocol we need to speak is there in send-pack.

Anyway, I'm going to try to get back to this topic more later
this week.  I have been focusing on JGit this week (or at least
trying to) as I really need to get some stuff done there for EGit.

-- 
Shawn.

      reply	other threads:[~2008-08-06 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  6:20 What's cooking in git.git (Aug 2008, #01; Tue, 05) Junio C Hamano
2008-08-06 14:21 ` Shawn O. Pearce [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080806142128.GA28231@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.