> Is there a best-practise for versioning a git snapshot? > At the moment I'm working towards something like: > > [new release number]~[commit count].g[commit hash abbrev] > > (inspired by git-describe HEAD) > > So if we'd packaged 0.1, then a git snap would be 0.2~42.g123456.
I'm using something similar. Since Git commit IDs are not sequential, it is recommended to use a sequential number (number of commits since the latest tag) that `git describe` returns at the tip of the upstream snapshot being packaged. For example, if: $ git describe v1.2-beta1-45-67890abc then package upstream version part of this snapshot could be 1.2~beta1+git45+67890abc. Cheers, Fathi _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
