threads / discuss / 34529

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

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

## tl;dr

2 messages between Jul 24, 2013 and Jul 24, 2013.

replies: 1people: 2as markdown or json

Jonathon Mah· Jul 24, 2013, 19:09 UTC · lore
>         Some git command (ex. git describe) by default only consider 
> annotated tags.
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)? I wasn't able to find any reason for the current behavior with just a little digging.

Jonathon Mah me@JonathonMah.com

Junio C Hamano· Jul 24, 2013, 20:37 UTC · re: Jonathon Mah · lore
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.

← back to recent threads