Re: Git-aware HTTP transport
- From
- H. Peter Anvin <hpa@zytor.com>
- Date
- Aug 28, 2008, 04:37 UTC
- Message-ID
- <48B62B6F.7010103@zytor.com>
- In-Reply-To
- <20080828035018.GA10010@spearce.org>
Shawn O. Pearce wrote:
Show 7 quoted lines
> > So this is what may be the final draft of the HTTP protocol. > I've added stuff about capability selection between the peers for > future expansion support. The upload-pack service has a better > use of it than receive-pack. Otherwise it is what I think you are > agreeing to above. ;-) >
It looks good to me. I *really* like the option of combining a redirect with a refs list in one reply; this will make things substantially easier do deploy on kernel.org, and saves a round trip to boot.
Just an implementation detail for the server, however: for an *empty* repository (one which has no refs at all), the server needs to *not* transmit the redirect, or there will be a loop :) It is unnecessary, anyway, since there is inherently nothing to do.
-hpa