On Sat, 2009-02-14 at 15:34 +0100, sean finney wrote: > hiya, > > On Sat, Feb 14, 2009 at 11:20:44AM +0100, David Paleino wrote: > > On Sat, 14 Feb 2009 11:17:42 +0100, Adeodato Simó wrote: > > > > > * Jonny Lamb [Fri, 13 Feb 2009 23:41:46 +0000]: > > > > > > > Version : 0.0.0+git+37ec0c > > > > > > I don't know what your further plans of versioning are for Git snapshot > > > (incrementing the micro release number?), but I thought I'd point out > > > that SHA1 are not sensibly sortable, just in case. > > > > Probably something like 0.0.0+git<num>~<sha> would work? Where <num> is > > incremented at each snapshot packaging. > > when i've had to do this in the past i think i did something like > <vers>~<YYYYMMDD>.git.<sha>. You might also be interested in the output of "git describe" which gives you <tag>-<nr-commits-since-tag>-g<sha1>, this is what CONFIG_LOCALVERSION_AUTO in the kernel uses (see scripts/setlocalversion). Since the tag would usually be the version number and nr-commits-since-tag always increases with a new commit this works ok. Ian. -- Ian Campbell C Code. C Code Run. Run, Code, RUN! PLEASE!!!!
Description: This is a digitally signed message part