From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Tom Preston-Werner <tom@github.com>, git@vger.kernel.org
Subject: Re: Local clone checks out wrong branch based on remote HEAD
Date: Tue, 17 Mar 2009 16:40:26 -0700 [thread overview]
Message-ID: <7viqm7pvkl.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0903171530160.19665@iabervon.org> (Daniel Barkalow's message of "Tue, 17 Mar 2009 15:39:55 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> ... I think there's also been discussion of a
> protocol extension to transmit the information, although I don't know
> where that ended up.
You can find them in the list of threads posted nearby.
The first round's protocol extension was not quite backward compatible
but in a benign way, in that it did not break anything but induced a
harmless warning from older ls-remote. The second round did not have such
flaw but it got a "Yuck".
From: Jeff King <peff@peff.net>
Date: Mon, 1 Dec 2008 12:44:15 -0500
Message-ID: <20081201174414.GA22185@coredump.intra.peff.net>
Subject: Re: [PATCH 5/6 (v2)] upload-pack: send the HEAD information
I somehow feel that the "Yuck" was addressed not to the patches but to the
problem the patch needs to address.
We could resurrect it if somebody is interested.
next prev parent reply other threads:[~2009-03-17 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 19:19 Local clone checks out wrong branch based on remote HEAD Tom Preston-Werner
2009-03-17 19:39 ` Daniel Barkalow
2009-03-17 23:40 ` Junio C Hamano [this message]
2009-03-18 1:51 ` Jeff King
2009-03-17 21:31 ` Nanako Shiraishi
2009-03-18 0:54 ` Jeff King
2009-03-18 10:05 ` Michael J Gruber
2009-03-18 21:11 ` Jay Soffian
2009-03-19 4:04 ` Jeff King
2009-03-19 4:02 ` Jeff King
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=7viqm7pvkl.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=tom@github.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).