-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The current v1.2 git tag is lightweight; please make it into an annotated tag #196
Comments
(Should probably also use |
@tianon, ideally, yes, but since Blackfriday v1.2 was released in August 2014, there has been some new features and flags, i.e. API changes, that Go applications like Hugo (https://github.com/spf13/hugo) now requires. (Hugo is probably the biggest user of the Blackfriday library.) I have not seen any recent talks about wrapping up the recent changes into a Blackfriday v1.3 release yet, so uploading a snapshot would be a good interim solution. |
I deleted the old tag, re-created it (backdated) as an annotated tag, and Thanks for pointing out the problem! On Tue, Sep 8, 2015 at 6:58 PM, Anthony Fok notifications@github.com
|
Thank you very much, Russ! |
Hello @russross,
While trying to update the blackfriday package for Debian, I was surprised that the automated
dh-make-golang
tool (https://github.com/Debian/dh-make-golang) created an erroneous upstream version of 1.1+git20150720.80.8cec3a8 when v1.2 was released a year ago.Digging deeper, it turns out that
dh-make-golang
got thev1.1
fromgit describe --abbrev=0
, skippingv1.2
becausev1.2
is currently a lightweight tag, whereasv1.1
andv1.0
were correctly tagged as annotated tags.Automated tools like
dh-make-golang
aside, I think it would confuse the end users too when they type ingit describe
and see this:I could get
git describe
to match v1.2 too by using--tags
, but it shouldn't be necessary:So yes, it would be great if you could fix that when you have time. It is a common problem (it is easy to forget to add the
-a
option when tagging), but the thankfully the fix is easy too, as described in the following Q&A and blog post:Thanks again!
Anthony
The text was updated successfully, but these errors were encountered: