git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Fully peel tags via for-each-ref?
Date: Mon, 19 Aug 2019 22:50:24 -0700	[thread overview]
Message-ID: <xmqq8srowfkv.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGyf7-GBx3FSCQTipmkNBtnwMANg5A0FXiiPc2az0NiRLRT+xg@mail.gmail.com> (Bryan Turner's message of "Mon, 19 Aug 2019 16:22:05 -0700")

Bryan Turner <bturner@atlassian.com> writes:

> Is there any way, with "git for-each-ref", to output the "fully"
> peeled SHA of a tag's ultimate target, regardless of how many layers
> must be traversed?

I do not think I wrote it to allow different degree of peeling, not
because I wanted to explicitly forbid a use case for tags that tag
another tag, but simply because I didn't think of anybody using it
and didn't see need to support such tags.

If %(*<stuff>) does not peel fully (I do not recall what I did
offhand), because all other things in Git (like $X~0, $X^{tree},
etc.) fully peel the outer object until they get to what they want,
it may even be OK to declare it a bug and "fix" the notation to
fully peel tags.  I dunno.

  reply	other threads:[~2019-08-20  5:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 23:22 Fully peel tags via for-each-ref? Bryan Turner
2019-08-20  5:50 ` Junio C Hamano [this message]
2019-08-20 21:39   ` Bryan Turner
2019-08-21 23:00   ` Jeff King
2019-08-22  3:07     ` Junio C Hamano
2019-08-22  4:24       ` 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=xmqq8srowfkv.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    /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).