1. 13 Oct, 2015 1 commit
    • Andrew Price's avatar
      Simplify version numbering using git tags · eea8fdc2
      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.18" 2.18
      
      so git describe will give us versions like 2.18-123-gf00baa which has
      better ordering properties than the current 2.18-gf00baa scheme, which
      is important for package upgrades. When HEAD matches the tag exactly, it
      will just give 2.18
      eea8fdc2
  2. 12 Oct, 2015 2 commits
  3. 08 Oct, 2015 3 commits
  4. 07 Oct, 2015 3 commits
  5. 06 Oct, 2015 9 commits
  6. 05 Oct, 2015 2 commits
  7. 02 Oct, 2015 2 commits
  8. 29 Sep, 2015 2 commits
  9. 25 Sep, 2015 1 commit
  10. 24 Sep, 2015 2 commits
  11. 23 Sep, 2015 1 commit
  12. 22 Sep, 2015 1 commit
  13. 21 Sep, 2015 3 commits
  14. 10 Sep, 2015 2 commits
  15. 30 Jul, 2015 2 commits
  16. 17 Jul, 2015 3 commits
  17. 16 Jul, 2015 1 commit