On Fri, Feb 7, 2014 at 5:52 PM, Andreas Beckmann <a...@debian.org> wrote:
> If your upstream is git, you don't have monotonically increasing > revision numbers, but (unordered) commit hashes. I usually use something > based on 'git describe' as that gives you a number of commits since a > reference tag in addition to a release. > > E.g. git describe returns 0.56-24-gffe37cd which is > <tag>-<number_of_commits_since_tag>-g<shortened_hash_of_HEAD> > and I would version the snapshot as 0.56+git24-gffe37cd. > > For git-based projects, I usually use a timestamp + commit id, e. g. 0.56+git201402061828-gffe37cd. Slightly longer but easier to understand and sorts as expected. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
