1. 04 May, 2015 2 commits
  2. 03 May, 2015 1 commit
  3. 27 Apr, 2015 5 commits
  4. 25 Apr, 2015 1 commit
    • Daniel Gollub's avatar
      Guess upstream-tag based on merge-base · aa8548d5
      Daniel Gollub authored
      In some unfortunate cases you might have something like this:
      
      $ git tag
      v1.0
      vyatta/1.0-0something1
      
      ... where later tag is closer to describe current HEAD.
      
      With upstream-tag set to v%(version)s find_tag() is going to propose
      something based on vyatta/1.0-0something1 which is not expected.
      
      The problem is that find_tag() returns tags, which match the
      upstream-tag format, but which are not on the upstream-branch at all.
      
      To fix this find_tag()/git-describe should not be used to determine
      the closest upstream-tag.
      
      Closes: gh#7
      aa8548d5
  5. 20 Apr, 2015 1 commit
  6. 02 Apr, 2015 1 commit
  7. 01 Apr, 2015 9 commits
  8. 27 Mar, 2015 20 commits