git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Q: git describe --always --tags .. gives "warning: tag 'tag1' is really 'tag2' here"

From
UWUlrich Windl <ulrich.windl@rz.uni-regensburg.de>
Date
May 29, 2019, 07:45 UTC
Message-ID
<5CEE38B4020000A1000317C6@gwsmtp.uni-regensburg.de>
Hi!
I have a project that changed its name some time ago (from "isredir" to "iredir"), so I added another tag for the same commit ID (What's the command to show the commit IDs for tags, BTW?: "git tag -v" does not.

As part of the build process, I run (for example) "git describe --always --tags af467c7". 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'm unsure what the message is actually saying: The hash cannot be resolved in a unique way?
I just see two tags remaining in refs:
> ls .git/refs/tags/
iredir-0.3.0  iredir-0.3.1

Regards, Ulrich

Next: Junio C Hamano
Message 1 of 4 in “Q: git describe --always --tags .. gives "warning: tag 'tag1' is really 'tag2' here"”
  1. Ulrich WindlMay 29, 2019
  2. Junio C HamanoMay 29, 2019
  3. Antw: Re: Q: git describe --always --tags .. gives "warning: tag 'tag1' is really 'tag2' here"Ulrich Windl, Jun 3, 2019
  4. Jeff KingJun 3, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.