Jeff King p...@peff.net writes:
It somehow feels a little weird to me that we would output the
information about refs/foo on the HEAD line.
I see that you realized why the above is not the case in the
downthread; the capability list is not about describing HEAD. The
list happens to be on the
On Fri, Sep 06, 2013 at 10:46:24AM -0700, Junio C Hamano wrote:
I think it is perfectly fine to expose _only_ HEAD now, and wait
until we find a good reason that we should send this information for
other symbolic refs in the repository.
Yeah, I agree with that.
However, because we already
On Sun, Sep 08, 2013 at 03:13:59AM -0400, Jeff King wrote:
What do you think about teaching git to read extra data after \0 for
_every_ ref line? And then ref advertisement might look something like:
sha1 HEAD\0multi_ack thin-pack ... symref=refs/heads/master\n
sha1 refs/heads/master\n
Andreas Krey a.k...@gmx.de writes:
From: Junio C Hamano gits...@pobox.com
This implements the server side of protocol extension to show which branch
the HEAD points at. The information is sent as a capability symref=target.
Signed-off-by: Junio C Hamano gits...@pobox.com
Signed-off-by:
Andreas Krey a.k...@gmx.de writes:
On Fri, 06 Sep 2013 10:46:24 +, Junio C Hamano wrote:
Andreas Krey a.k...@gmx.de writes:
...
reason later, on-the-wire format should be prepared to support such
later enhancement. I think sending
symref=HEAD:refs/heads/master
5 matches
Mail list logo
