From: Bryan Turner <bturner@atlassian.com>
To: Git Users <git@vger.kernel.org>
Subject: Fully peel tags via for-each-ref?
Date: Mon, 19 Aug 2019 16:22:05 -0700 [thread overview]
Message-ID: <CAGyf7-GBx3FSCQTipmkNBtnwMANg5A0FXiiPc2az0NiRLRT+xg@mail.gmail.com> (raw)
When running "git for-each-ref", it's possible to use %(*objectname)
to get the SHA of the object a tag is tagging, and %(*objecttype) to
get the type. However, in the case of an annotated tag of an annotated
tag, this still isn't "fully" peeled--%(*objectname) is the tagged
tag's SHA.
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?
Best regards,
Bryan Turner
next reply other threads:[~2019-08-19 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 23:22 Bryan Turner [this message]
2019-08-20 5:50 ` Fully peel tags via for-each-ref? Junio C Hamano
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=CAGyf7-GBx3FSCQTipmkNBtnwMANg5A0FXiiPc2az0NiRLRT+xg@mail.gmail.com \
--to=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).