Re: version format for git snapshot

2015-09-14 Thread Jonas Smedegaard
Quoting Pau Garcia i Quiles (2015-09-14 12:23:57) > > On Monday, September 14, 2015, Jonas Smedegaard wrote: >> Makes perfect sense to me to add only the date for snapshot releases >> - both revision control system and commit id is irrelevant in version >> string - those belong

Re: version format for git snapshot

2015-09-14 Thread Neil Williams
On Mon, 14 Sep 2015 07:51:09 +0200 Thomas Koch wrote: > Hi, > > my upstream tagged 0.4 a year ago and I want to package the current > master commit a5e5f9e that is 24 commits after 0.4. Please assume > that this makes sense... > > How would you format the upstream part of the

Re: version format for git snapshot

2015-09-14 Thread The Wanderer
On 2015-09-14 at 05:04, Jakub Wilk wrote: > * Pau Garcia i Quiles , 2015-09-14, 10:46: > >> 0.5+git20150531T211420-cdd9d98f2c-1~vivid~pgquiles1 > > Still shorter than > 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1. You're not > trying hard enough. I am reminded of

Re: version format for git snapshot

2015-09-14 Thread Colin Watson
On Mon, Sep 14, 2015 at 10:46:10AM +0200, Pau Garcia i Quiles wrote: > On Mon, Sep 14, 2015 at 8:51 AM, Colin Watson wrote: > > I wouldn't put the commit identifier in the package version at all. It > > isn't sortable, so clearly doesn't belong in a version string; it can be

Re: version format for git snapshot

2015-09-14 Thread Pau Garcia i Quiles
On Tue, Sep 15, 2015 at 1:24 AM, Colin Watson wrote: > > This is what I generally do: last release + "git" + ISO 8601 date and > time > > + 10-char substring of the commit id. I. e: > > > > 0.5+git20150531T211420-cdd9d98f2c-1 > > IME it is in fact useful to have version

Re: version format for git snapshot

2015-09-14 Thread Colin Watson
On Mon, Sep 14, 2015 at 07:51:09AM +0200, Thomas Koch wrote: > How would you format the upstream part of the packages version number? How > about 0.4+24+git+a5e5f9e? I wouldn't put the commit identifier in the package version at all. It isn't sortable, so clearly doesn't belong in a version

Re: version format for git snapshot

2015-09-14 Thread Thomas Goirand
On 09/14/2015 07:51 AM, Thomas Koch wrote: > Hi, > > my upstream tagged 0.4 a year ago and I want to package the current master > commit a5e5f9e that is 24 commits after 0.4. Please assume that this makes > sense... > > How would you format the upstream part of the packages version number? How

Re: version format for git snapshot

2015-09-14 Thread Jonas Smedegaard
Hi Thomas, Quoting Thomas Koch (2015-09-14 07:51:09) > my upstream tagged 0.4 a year ago and I want to package the current > master commit a5e5f9e that is 24 commits after 0.4. Please assume that > this makes sense... > > How would you format the upstream part of the packages version number?

Re: version format for git snapshot

2015-09-14 Thread Eduard Bloch
Hallo, * Thomas Koch [Mon, Sep 14 2015, 07:51:09AM]: > Hi, > > my upstream tagged 0.4 a year ago and I want to package the current master > commit a5e5f9e that is 24 commits after 0.4. Please assume that this makes > sense... > > How would you format the upstream part of the packages version

Re: version format for git snapshot

2015-09-14 Thread Andreas Henriksson
Hello Thomas Koch! On Mon, Sep 14, 2015 at 07:51:09AM +0200, Thomas Koch wrote: > Hi, > > my upstream tagged 0.4 a year ago and I want to package the current master > commit a5e5f9e that is 24 commits after 0.4. Please assume that this makes > sense... > > How would you format the upstream

Re: version format for git snapshot

2015-09-14 Thread Pau Garcia i Quiles
On Mon, Sep 14, 2015 at 11:04 AM, Jakub Wilk wrote: * Pau Garcia i Quiles , 2015-09-14, 10:46: > >> 0.5+git20150531T211420-cdd9d98f2c-1~vivid~pgquiles1 >> > > Still shorter than 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1. > You're not trying hard

Re: version format for git snapshot

2015-09-14 Thread Jonas Smedegaard
Quoting Colin Watson (2015-09-14 08:51:48) > On Mon, Sep 14, 2015 at 07:51:09AM +0200, Thomas Koch wrote: >> How would you format the upstream part of the packages version >> number? How about 0.4+24+git+a5e5f9e? > > I wouldn't put the commit identifier in the package version at all. > It isn't

Re: version format for git snapshot

2015-09-14 Thread Pau Garcia i Quiles
On Mon, Sep 14, 2015 at 8:51 AM, Colin Watson wrote: On Mon, Sep 14, 2015 at 07:51:09AM +0200, Thomas Koch wrote: > > How would you format the upstream part of the packages version number? > How > > about 0.4+24+git+a5e5f9e? > > I wouldn't put the commit identifier in the

Re: version format for git snapshot

2015-09-14 Thread Jakub Wilk
* Pau Garcia i Quiles , 2015-09-14, 10:46: 0.5+git20150531T211420-cdd9d98f2c-1~vivid~pgquiles1 Still shorter than 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1. You're not trying hard enough. -- Jakub Wilk

Re: version format for git snapshot

2015-09-14 Thread Pau Garcia i Quiles
On Monday, September 14, 2015, Jonas Smedegaard wrote: Makes perfect sense to me to add only the date for snapshot releases - > both revision control system and commit id is irrelevant in version > string - those belong (if at all) in changelog along with release > nickname and

version format for git snapshot

2015-09-13 Thread Thomas Koch
Hi, my upstream tagged 0.4 a year ago and I want to package the current master commit a5e5f9e that is 24 commits after 0.4. Please assume that this makes sense... How would you format the upstream part of the packages version number? How about 0.4+24+git+a5e5f9e? The git describe output is