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

Suggestion: error "tag ... already exists" should distinguish between tagging different or same commit:

From
M Hickford <mirth.hickford@gmail.com>
Date
Jun 9, 2025, 07:00 UTC
Message-ID
<CAGJzqsnvTnp3k8Ab2exaBAw5pszQRz00UcucnK=ECtY5vhG+1A@mail.gmail.com>

Hi. Presently, the error "tag ... already exists" doesn't distinguish between tagging the same commit or a different commit:

     >git tag hello v1.9.5
     >git tag hello v1.9.5
     fatal: tag 'hello' already exists
     >git tag hello v2.0.0
     fatal: tag 'hello' already exists
To inform the user, it would be nice to distinguish these cases, perhaps:
     >git tag hello v1.9.5
     fatal: tag 'hello' already exists pointing at
d4e6038a068d0aecd5ec28c83afbfc6d4903092f
     >git tag hello v2.0.0
     fatal: tag 'hello' already exists but points at
18a07354e33f86c8349ffdc300d9087876658264
The second error is typically more concerning than the first.
What do you think?
Next: Junio C Hamano
Message 1 of 14 in “Suggestion: error "tag ... already exists" should distinguish between tagging different or same commit:”
  1. M HickfordJun 9, 2025
  2. Junio C HamanoJun 9, 2025
  3. Hilco WijbengaJun 9, 2025
  4. Andreas SchwabJun 9, 2025
  5. Junio C HamanoJun 9, 2025
  6. Hilco WijbengaJun 9, 2025
  7. M HickfordJun 10, 2025
  8. Junio C HamanoJun 10, 2025
  9. Junio C HamanoJul 7, 2025
  10. rsbecker@nexbridge.comJul 7, 2025
  11. Junio C HamanoJul 11, 2025
  12. tag: allow idempotent "git tag" without "--force"Junio C Hamano, Jul 11, 2025
  13. Justin ToblerJul 11, 2025
  14. Junio C HamanoJul 11, 2025

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.