git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Utku <ugultopu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to get the branch HEAD points to using a plumbing command?
Date: Tue, 05 Jan 2021 14:55:12 -0800	[thread overview]
Message-ID: <xmqqy2h7xacv.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <132D030A-AAD3-4EFC-9858-7EA39503A746@gmail.com> (Utku's message of "Tue, 5 Jan 2021 10:09:47 -0500")

Utku <ugultopu@gmail.com> writes:

> My question is, is there a "better" (more idiomatic, less
> "expensive", etc.) way of doing it using only one plumbing
> command? This solution is OK but it is more work than just
> matching one line with a regular expression. The reason I want to
> do this using only plumbing commands is because I think that
> plumbing command interface would be more stable than the format
> (organization, structure) of files under the `.git/` directory
> across Git versions. Please correct me if I'm wrong in this idea
> as well.

The "HEAD" pointer can be a symbolic link, not a text file with
"ref: refs/heads/..." in it, and any approach that works directly
with "cat .git/HEAD" would be incorrect, unless it does a stat on
.git/HEAD first to see if it is a symlink.  And such implementation
details can change over time.

So you are right to seek a solution that hides such details from
you, i.e. a Git command, to do so.  It does not have to be plumbing,
though.

The orthodox answer would be to use "git symbolic-ref".  When you
want to learn which underlying ref a symbolic ref is pointing at,
that is the tool designed to answer that question.

      parent reply	other threads:[~2021-01-05 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 15:09 How to get the branch HEAD points to using a plumbing command? Utku
2021-01-05 15:24 ` Ævar Arnfjörð Bjarmason
2021-01-05 20:01   ` Jeff King
2021-01-05 22:55 ` Junio C Hamano [this message]

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=xmqqy2h7xacv.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ugultopu@gmail.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).