From: Luke Diamand <luke@diamand.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: [PATCHv1 2/2] git-p4: work with a detached head
Date: Wed, 28 Oct 2015 19:03:03 +0000 [thread overview]
Message-ID: <56311BE7.6090204@diamand.org> (raw)
In-Reply-To: <xmqqfv0ulwgj.fsf@gitster.mtv.corp.google.com>
On 28/10/15 17:44, Junio C Hamano wrote:
> Luke Diamand <luke@diamand.org> writes:
>
>> On 9 September 2015 at 22:52, Junio C Hamano <gitster@pobox.com> wrote:
>>> Luke Diamand <luke@diamand.org> writes:
>>> ...
>>> def currentGitBranch():
>>> return read_pipe("git name-rev HEAD").split(" ")[1].strip()
>>>
>>> Yuck. I know it is not entirely the fault of this patch, but
>>> shouldn't it be reading from
>>>
>>> $ git symbolic-ref HEAD
>>>
>>> and catch the error "fatal: ref HEAD is not a symbolic ref" and use
>>> it as a signal to tell that the HEAD is detached?
>>
>> That sounds much nicer. I'll redo the patch accordingly.
>
> No need to rush, but should I expect a reroll of this sometime, or
> have things around this topic changed to make this topic no longer
> necessary? I am only asking so that I can decide to either keep or
> drop ld/p4-detached-head topic that is listed in the [Stalled]
> section for quite some time [*1*].
I was waiting for the other git-p4 changes to go through before starting
this up again.
It definitely needs fixing - it was annoying me a lot today, as I kept
on having to invent temporary branch names to needlessly keep git-p4 happy.
After getting to "for-p4-9", I'm now onto "xyyyy". I'll see if I can
sort something out in the next few days.
Luke
>
> Thanks.
>
>
> [Footnote]
>
> *1* Not that my dropping a topic from 'pu' means very much; a
> dropped topic can still be submitted and requeued after all.
>
next prev parent reply other threads:[~2015-10-28 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 14:02 [PATCHv1 0/2] git-p4: work on a detached head Luke Diamand
2015-09-05 14:02 ` [PATCHv1 1/2] git-p4: add failing test for submit from " Luke Diamand
2015-09-05 14:02 ` [PATCHv1 2/2] git-p4: work with a " Luke Diamand
2015-09-09 21:52 ` Junio C Hamano
2015-09-10 7:29 ` Luke Diamand
2015-09-10 16:20 ` Junio C Hamano
2015-10-28 17:44 ` Junio C Hamano
2015-10-28 19:03 ` Luke Diamand [this message]
2015-09-09 12:03 ` [PATCHv1 0/2] git-p4: work on " Lars Schneider
2015-09-10 1:57 ` Jacob Keller
2015-09-10 1:59 ` Jacob Keller
2015-09-10 12:23 ` Luke Diamand
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=56311BE7.6090204@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).