From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Subject: Re: Trouble with cat-file on tags
Date: Fri, 1 Apr 2016 12:00:44 +0200 [thread overview]
Message-ID: <ndlgsc$ed7$1@ger.gmane.org> (raw)
In-Reply-To: <ndlf7q$ghe$1@ger.gmane.org>
On 4/1/2016 11:32, Sebastian Schuberth wrote:
> However, I still get information about the commit oject iintsead of the
> tag object. Is this expected?
Solved this one, too: Yes it is. I was misreading the docs:
"If <type> is specified, the raw (though uncompressed) contents of the
<object> will be returned."
This means
$ git cat-file tag refs/tags/v0.1.2
displays the *contents* of the tag, not the tag itself. Which leads me
to the next question: For a given name of an annotated tag, how to get
the hash of the tag object? The solution I found for now:
$ git show-ref --tags -- v0.1.2
92b67e2b0626519ef8cd4e9cacb2bdafba6d53f0 refs/tags/v0.1.2
Regards,
Sebastian
next prev parent reply other threads:[~2016-04-01 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 9:26 Trouble with cat-file on tags Sebastian Schuberth
2016-04-01 9:32 ` Sebastian Schuberth
2016-04-01 10:00 ` Sebastian Schuberth [this message]
2016-04-01 12:26 ` 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='ndlgsc$ed7$1@ger.gmane.org' \
--to=sschuberth@gmail.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).