From: Junio C Hamano <gitster@pobox.com>
To: Andreas Krey <a.krey@gmx.de>
Cc: Michael Schubert <mschub@elegosoft.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Remote's 'currently active branch' not HEAD?
Date: Tue, 03 Sep 2013 08:33:39 -0700 [thread overview]
Message-ID: <xmqqd2opvs18.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20130903135034.GS12966@inner.h.apk.li> (Andreas Krey's message of "Tue, 3 Sep 2013 15:50:34 +0200")
Andreas Krey <a.krey@gmx.de> writes:
> On Tue, 03 Sep 2013 15:02:50 +0000, Michael Schubert wrote:
> ...
>> > happen to have the HEAD *commit* as their tip.
>>
>> Yes, it picks the first of those:
>>
>> http://thread.gmane.org/gmane.comp.version-control.git/168144
>
> Thanks for the pointer.
>
> And pity, the patches didn't make it that time either...
And the key article in that discussion by Peff points to
http://thread.gmane.org/gmane.comp.version-control.git/102039 with
"I had some complaints at the time, but re-reading it I don't see
anything that would prevent us from revisiting the topic now."
Reading the patch series from 2008 again, I do agree with J6t's
comment that it should be just a regular capability, i.e. like what
Peff suggests in his comment on [PATCH 5/6 (v2)], but other than
that, I do not see anything that would prevent us from revisiting
the topic now, either.
next prev parent reply other threads:[~2013-09-03 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 10:46 Remote's 'currently active branch' not HEAD? Andreas Krey
2013-09-03 11:48 ` Andreas Krey
2013-09-03 12:37 ` Andreas Krey
2013-09-03 13:02 ` Michael Schubert
2013-09-03 13:50 ` Andreas Krey
2013-09-03 15:33 ` Junio C Hamano [this message]
2013-09-06 11:41 ` Andreas Krey
2013-09-06 12:54 ` Andreas Krey
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=xmqqd2opvs18.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=a.krey@gmx.de \
--cc=git@vger.kernel.org \
--cc=mschub@elegosoft.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.