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

Regression? Ambiguous tags listed as "tags/<foo>"

From
PHPete Harlan <pgit@tento.net>
Date
Jan 23, 2016, 23:56 UTC
Message-ID
<CAAB=nN=RSQuDPdg6Y2heeBXpQVdWSwFAcDDTfxE=XRSOu5gGEg@mail.gmail.com>

There was a behavior change in "git tag" in b7cc53e9 (tag.c: use 'ref-filter' APIs, 2015-07-11, v2.5.0-276-gb7cc53e), such that "git tag" now writes "foo" as "tags/foo" if there is also a branch named "foo":

    % git tag
    tags/branchortag
    tagonly
Previous behavior:
    % git tag
    branchortag
    tagonly

I prefer the previous behavior. Perhaps the change was intentional, but I didn't see it documented.

Thanks,

Pete Harlan pgit@tento.net

Next: Jeff King
Message 1 of 19 in “Regression? Ambiguous tags listed as "tags/<foo>"”
  1. Pete HarlanJan 23, 2016
  2. tag: do not show ambiguous tag names as "tags/foo"Jeff King, Jan 24, 2016
  3. Jeff KingJan 24, 2016
  4. Junio C HamanoJan 24, 2016
  5. Jeff KingJan 24, 2016
  6. Eric SunshineJan 24, 2016
  7. Jeff KingJan 25, 2016
  8. Junio C HamanoJan 25, 2016
  9. Jeff KingJan 25, 2016
  10. Karthik NayakJan 25, 2016
  11. Junio C HamanoJan 25, 2016
  12. Jeff KingJan 26, 2016
  13. Jeff KingJan 26, 2016
  14. Junio C HamanoJan 26, 2016
  15. Jeff KingJan 24, 2016
  16. 1/2 t6300: use test_atom for some un-modern testsJeff King, Jan 24, 2016
  17. 2/2 tag: do not show ambiguous tag names as "tags/foo"Jeff King, Jan 24, 2016
  18. Junio C HamanoJan 26, 2016
  19. Karthik NayakJan 26, 2016

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.