From: Junio C Hamano <gitster@pobox.com>
To: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
Cc: <git@vger.kernel.org>
Subject: Re: Q: git describe --always --tags .. gives "warning: tag 'tag1' is really 'tag2' here"
Date: Wed, 29 May 2019 11:01:38 -0700 [thread overview]
Message-ID: <xmqqd0k1ywal.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <5CEE38B4020000A1000317C6@gwsmtp.uni-regensburg.de> (Ulrich Windl's message of "Wed, 29 May 2019 09:45:56 +0200")
"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> writes:
> So I got the response:
> warning: tag 'isredir-0.3.0' is really 'iredir-0.3.0' here
> isredir-0.3.0-3-gaf467c7
I suspect that "git cat-file tag isredir-0.3.0" would begin like
$ git cat-file tag iredir-0.3.0
object .....
type commit
tag isredir-0.3.0
tagger ...
Notice that "tag" line records the true name of that tag, which does
not match where you stored that tag in refs/tags/ hierarchy?
While trying to describe af467c7 by following its ancestry and
finding the ancestor three generations ago, the command found
refs/tags/iredir-0.3.0 and then noticed that discrepancy, which is
what the warning is about.
Imagine you have only v1.0.0 (which is with known issues) but
somebody did "cd .git/refs/tags && mv v1.0.0 v1.1.0" in an attempt
to fool you. The fact that your 'master' is a bit ahead of the
commit that was tagged with the tag object (which is v1.0.0 but
pretending to be v1.1.0) can be seen with "describe", but the
command is careful enough to use the real version number
(i.e. v1.0.0) and not the refname (i.e. v1.1.0).
next prev parent reply other threads:[~2019-05-29 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 7:45 Q: git describe --always --tags .. gives "warning: tag 'tag1' is really 'tag2' here" Ulrich Windl
2019-05-29 18:01 ` Junio C Hamano [this message]
2019-06-03 6:06 ` Antw: " Ulrich Windl
2019-06-03 10:55 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd0k1ywal.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).