From: Bryan Turner <bturner@atlassian.com>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: v2.9.3 and v2.10.0: `name-ref' HEAD gives wrong branch name
Date: Tue, 20 Sep 2016 11:54:37 -0700 [thread overview]
Message-ID: <CAGyf7-FR11Ludt3vNZX7Ek4n_JLSON5+Y9By83GvNgpg94TWcg@mail.gmail.com> (raw)
In-Reply-To: <20160920162309.l0neYMQ3l%steffen@sdaoden.eu>
On Tue, Sep 20, 2016 at 9:23 AM, Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
> Hello again,
>
> yah, sorry, i'm back again..
> I try to find a way to find the name of the current branch in an
> automated way, because i need to ensure that a commit happens on
> it and no other branch. Now the problem arises that the commit
> ref at the time of that commit maybe shared in between several
> different branches, but no more thereafter, of course:
>
> ?0[steffen@wales ]$ git branch|grep '^*'
> * stable/v14.9
> ?0[steffen@wales ]$ git name-rev --name-only HEAD
> stable/v14.8
>
> Is there another way except looking into .git/HEAD or using sed(1)
> on the output of `branch' to find the right name?
Have you tried "git symbolic-ref HEAD"?
$ git symbolic-ref HEAD
refs/heads/master
If you don't want the fully-qualified ref, you can add --short:
$ git symbolic-ref --short HEAD
master
> Thank you.
> Ciao!
>
> --steffen
next prev parent reply other threads:[~2016-09-20 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 16:23 v2.9.3 and v2.10.0: `name-ref' HEAD gives wrong branch name Steffen Nurpmeso
2016-09-20 18:54 ` Bryan Turner [this message]
2016-09-20 19:29 ` Steffen Nurpmeso
2016-09-21 13:43 ` Jakub Narębski
2016-09-21 14:21 ` Steffen Nurpmeso
2016-09-21 16:37 ` Junio C Hamano
2016-09-21 17:54 ` Jakub Narębski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGyf7-FR11Ludt3vNZX7Ek4n_JLSON5+Y9By83GvNgpg94TWcg@mail.gmail.com \
--to=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=steffen@sdaoden.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).