From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/4] server info: Add HEAD to info/refs
Date: Thu, 26 Apr 2007 21:36:00 -0700 [thread overview]
Message-ID: <7vps5qph73.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070427042802.GW4489@pasky.or.cz> (Petr Baudis's message of "Fri, 27 Apr 2007 06:28:02 +0200")
Petr Baudis <pasky@suse.cz> writes:
> On Fri, Apr 27, 2007 at 05:51:36AM CEST, Junio C Hamano wrote:
>> I always considered it was a bug that the native transport sends
>> SHA-1 of HEAD after dereferencing the symref, instead of saying
>> which branch it points at.
>
> Yes, you are right. That was what I was originally after, but then got
> sidetracked into working on something else and this easy bit was the
> only thing left done, so I just passed it along. :)
>
>> How about proceeding along these lines?
>
> Looks generally good.
>
>> * We add native protocol extension to let upload-pack to say
>> what HEAD symref points at, in addition to the SHA-1 HEAD
>> points at. Update peek-remote to show this information like
>> this:
>>
>> ->refs/heads/master<TAB>HEAD<LF>
>> 0d5e6c97...<TAB>HEAD<LF>
>> ...
>
> Yet another obscure syntax? Why not just reusing the actual ref: syntax?
Yup, ref: is fine. Please make it so, but after 1.5.2 ;-).
next prev parent reply other threads:[~2007-04-27 4:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 2:06 [PATCH 1/4] Git.pm: config_boolean() -> config_bool() Petr Baudis
2007-04-27 2:06 ` [PATCH 2/4] Git.pm: Add remote_refs() git-ls-remote frontend Petr Baudis
2007-04-27 2:06 ` [PATCH 3/4] [PATCH] git-mirror - exactly mirror another repository Petr Baudis
2007-04-27 4:39 ` Shawn O. Pearce
2007-04-27 2:06 ` [PATCH 4/4] server info: Add HEAD to info/refs Petr Baudis
2007-04-27 3:51 ` Junio C Hamano
2007-04-27 4:28 ` Petr Baudis
2007-04-27 4:36 ` Junio C Hamano [this message]
2007-04-28 6:27 ` [PATCH 1/4] Git.pm: config_boolean() -> config_bool() Junio C Hamano
2007-05-09 10:49 ` [PATCH] " Petr Baudis
2007-05-09 15:13 ` Petr Baudis
2007-05-10 2:12 ` Junio C Hamano
2007-05-09 15:24 ` Junio C Hamano
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=7vps5qph73.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.