From: Jeff King <peff@peff.net>
To: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Cc: Roland Hieber <rhi@pengutronix.de>, git <git@vger.kernel.org>
Subject: Re: git-describe --tags warning: 'X' is really 'Y' here
Date: Fri, 14 Feb 2020 01:53:52 -0500 [thread overview]
Message-ID: <20200214065352.GG605125@coredump.intra.peff.net> (raw)
In-Reply-To: <CAHd-oW6p-zs-SZnQsJNWPGE8-Ls3vXvf_HOeO+W=1PsQ_oihZA@mail.gmail.com>
On Wed, Feb 05, 2020 at 02:15:07PM -0300, Matheus Tavares Bernardino wrote:
> > I'm working with the GCC Git repo [0] (which was apparently recently
> > converted from SVN [1]), and I'm trying to find out the most recent tag.
> > So on the master branch I do:
> >
> > gcc (master) $ git describe --tags --abbrev=0
> > warning: tag 'gcc_9_2_0_release' is really 'releases/gcc-9.2.0' here
> > gcc_9_2_0_release
> >
> > It took me a while to find out what the warning means, because
> > 'gcc_9_2_0_release' is not in $(git tag -l), and it cannot be used as a
> > ref either:
> [...]
> It seems that the commit which added the output message you got is
> 212945d ("Teach git-describe to verify annotated tag names before
> output", 2008-02-28) [1]. As the commit message states, the warning is
> emitted when a tag is locally stored under a different name from the
> one it was originally created (being the former the one you will want
> to use at `git show`).
Yeah, I think that is what's going on with that warning, but there's a
weird thing about the actual stdout output. We see a tag object whose
name doesn't match the ref. What's the "real" name of that tag? Is it
the name in the object, and the ref is wrong? Or is the ref correct, and
the object is wrong?
You could get pretty philosophical there, I think, but it seems slightly
annoying that we print the name from the object to stdout, when one
cannot then use that name to access the tag in any way.
I.e., I think it might be reasonable to issue that warning but then
print "releases/gcc-9.2.0" instead.
-Peff
next prev parent reply other threads:[~2020-02-14 6:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 14:13 git-describe --tags warning: 'X' is really 'Y' here Roland Hieber
2020-02-05 17:15 ` Matheus Tavares Bernardino
2020-02-14 6:53 ` Jeff King [this message]
2020-02-14 16:57 ` Junio C Hamano
2020-02-15 21:34 ` [PATCH] describe: output tag's ref instead of embedded name Matheus Tavares
2020-02-16 6:51 ` Jeff King
2020-02-18 19:31 ` Junio C Hamano
2020-02-18 19:54 ` Jeff King
2020-02-18 23:05 ` Junio C Hamano
2020-02-18 23:28 ` Junio C Hamano
2020-02-19 1:57 ` Jeff King
2020-02-19 3:22 ` Junio C Hamano
2020-02-19 3:56 ` Jeff King
2020-02-19 11:14 ` Junio C Hamano
2020-02-20 11:25 ` Jeff King
2020-02-20 17:34 ` Junio C Hamano
2020-02-20 22:19 ` Matheus Tavares Bernardino
2020-02-20 22:59 ` Junio C Hamano
2020-02-21 1:33 ` Matheus Tavares
2020-02-21 2:05 ` Junio C Hamano
2020-02-21 6:00 ` Jeff King
2020-02-21 5:58 ` Jeff King
2020-02-19 10:08 ` Roland Hieber
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=20200214065352.GG605125@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=matheus.bernardino@usp.br \
--cc=rhi@pengutronix.de \
/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).