search

pccasto / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

tag/mark releases in git #278

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. use git and try to checkout a previous version, e.g. with
git checkout v0.5.4

...

Please provide any additional information below.
This is common in other projects (wine, kernel,...) because with those
marks and the function "git bisect" you can find patches which causes
regressions in your program, like bug 277 I posted earlier.

Original issue reported on code.google.com by jbuec...@gmail.com on 6 Feb 2009 at 12:56

GoogleCodeExporter commented 8 years ago 
This is a valid request.

Notice that git is something new to me as well :)

Can you get any reference how to apply those tags as an afterthought?

Original comment by rubyripp...@gmail.com on 6 Feb 2009 at 4:23

GoogleCodeExporter commented 8 years ago 
Not really, I didn't apply a patch with git myself yet.

Maybe like this on command line

git tag v0.5.5 74006b098dcc47494b7fce7c32db0e25abfcb1fd

if 74006b098dcc47494b7fce7c32db0e25abfcb1fd was the last patch before the 
release, or
with gitk.

I found this for more info:
http://www.kernel.org/pub/software/scm/git/docs/git-tag.html

Original comment by jbuec...@gmail.com on 7 Feb 2009 at 1:49

GoogleCodeExporter commented 8 years ago 
I will tag next release, but I'm afraid tagging as an afterthought isn't that 
easy.

Original comment by rubyripp...@gmail.com on 15 Apr 2009 at 6:21