Hello Fra, On 10/12/2018 14:28, Francesco Mari wrote: > Using a version composed by based version, timestamp and commit hash works > well. The qualifier is compared lexicographically, so the timestamp would > do the trick regardless of the commit hash. See this example [1] on > Versionatorr.
you put 1.0-20181210-79377d5aab231f27fa7e3dc7bdd0e828 1.0-20181209-8135fa0dc4bdb394f38afc1f084336a2 which are two different timestamps. I didn't look yet at the details nor if this *would actually happen* *Release 1* HEAD 20121210 | | ... Will produce X.Y-20121210-79377d *Release 2* We want to release something that has just been merged but the merge doesn't move HEAD HEAD 20121210 | | \ | \ BRANCH 20121215 8135fa0dc ... ... Will produce again X.Y-20121210-79377d but in fact are two different binaries. Does git change always HEAD? Even if you merge something that fits "behind" HEAD. Davide
