Commits on Source (2)
-
Andrew Price authored
As we're determined to use git for providing version numbers we might as well do it the right way. Take all of the version information from git describe. This assumes that at least one annotated tag exists in the branch relating to a release. The tag will be created using $ git tag -a -m "Version 2.17" 2.17 fb1be771 so git describe will give us versions like 2.17-123-gf00baa which has better ordering properties than the current 2.17-gf00baa scheme, which is important for package upgrades. When HEAD matches the tag exactly, it will just give 2.17
9325a02d -
Andrew Price authored79336cc6