Skip Menu |

This queue is for tickets about the Dist-Zilla-Plugin-Git CPAN distribution.

Report information
The Basics
Id: 55352
Status: resolved
Priority: 0/
Queue: Dist-Zilla-Plugin-Git

People
Owner: Nobody in particular
Requestors: bpphillips+bitcard [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: the git tag that is created should be an annotated tag
Using annotated tags (as opposed to "lightweight" tags) allows `git describe` to work as expected. All this requires is adding a "-m" option on the `git tag` command: % git tag -m <mesg> <tag> The <mesg> could be as simple as the tag that is being created.
On Mon Mar 08 13:58:16 2010, bphillips wrote: Show quoted text
> Using annotated tags (as opposed to "lightweight" tags) allows `git > describe` to work as expected. All this requires is adding a "-m" option > on the `git tag` command: > % git tag -m <mesg> <tag> > > The <mesg> could be as simple as the tag that is being created.
are we sure we want this? in that case, the tag becomes a commit. note that "git describe --tags" works with lightweight tags. i'm not saying i won't implement it, i'm just discussing the various alternatives...
On Mon Mar 08 14:18:35 2010, JQUELIN wrote: Show quoted text
> are we sure we want this? in that case, the tag becomes a commit. > note that "git describe --tags" works with lightweight tags. > > i'm not saying i won't implement it, i'm just discussing the various > alternatives...
I was unaware of the --tags option to `git describe` but you're right, that seems to make it work. I was kind of going on the assumption that the following (cribbed from http://learn.github.com/p/tagging.html) is generally accepted: "There are a two main types of tags in Git - lightweight and annotated. Lightweight tags are very much like branches that don’t change - it’s just a pointer to a specific commit. Annotated tags, however, are stored as full objects in the Git database. They are checksummed, contain the tagger name, email and date, have a tagging message and can be GPG signed and verified. It’s generally recommended to create annotated tags so you can have all this information, but if you want a temporary tag or for some reason don’t want to keep that other information, lightweight tags are available too."
On Mon Mar 08 14:25:18 2010, bphillips wrote: Show quoted text
> I was kind of going on the assumption that > the following (cribbed from http://learn.github.com/p/tagging.html) > is generally accepted: > > "There are a two main types of tags in Git - lightweight and annotated. > Lightweight tags are very much like branches that don’t change - it’s > just a pointer to a specific commit. Annotated tags, however, are stored > as full objects in the Git database. They are checksummed, contain the > tagger name, email and date, have a tagging message and can be GPG > signed and verified. It’s generally recommended to create annotated tags > so you can have all this information, but if you want a temporary tag or > for some reason don’t want to keep that other information, lightweight > tags are available too."
ok, annotated tags don't appear as a commit of their own in history. as such, they won't be a big disruption to previous behaviour. ==> i'll implement it.
fixed in v1.100680