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

Re: git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default)

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 24, 2013, 20:37 UTC
Message-ID
<7vppu766ev.fsf@alter.siamese.dyndns.org>
In-Reply-To
<032D5084-C70F-4F62-8F62-975ADEA56ED6@JonathonMah.com>
Jonathon Mah <me@JonathonMah.com> writes:
> I always add --tags when I call git-describe. Is there any reason this shouldn't become the new default (quickly, before git 2.0 perhaps)?

The distinction is there for a reason--- annotated tags are meant for the more "public" and "permanent" stuff, while you can do lightweight tags for random short-term stuff.

An argument could be to change Git not to follow unannotated tags with "git fetch" and "git push --follow-tags" by default, which goes in the direction to make the distinction even clear. But for a change to make the distinction less useful, I would have to say it is probably a bad idea.

Previous: Jonathon Mah
Message 2 of 2 in “Re: git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default)”
  1. Jonathon MahJul 24, 2013
  2. Junio C HamanoJul 24, 2013

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.