|
|
Re: Using TortoiseGIT
01/15/15 11:15 AM
|
|
|
> > You could have at least pretended not to be a jerk and told him that the GIT
> > equivalent to a revision number is a commit ID (no, I don't know how to make
> > TortoiseGIT tell you the commit ID after doing a pull).
>
> That wasn't a jerk response, yours was. Good luck remembering and comparing those
> commit ID's.
Yes, I realise there's no way to easily compare two of them. But they're still the correct way to uniquely identify a revision, e.g. for identifying when a regression occurs, or to tell someone which revision you built from. Also, git gives you the number of revisions since last annotated tag, so that can serve as a "revision number". On the command line, you do this with "git describe", e.g. with a rather outdated tree:
Code:
# git describe
mame0156-182-g91e3597
This tells you that the most recent annotated tag was mame0156, there have been 182 revisions committed since the tag, and the current revision's commit ID is 91e3597. The number will increment nicely on each commit until the next annotated tag. And no, I don't know how to get this with the turtle, only command line.
|
|
Index 
Flat 
Re: Using TortoiseGIT
Reply
