On 28/01/2013 18:21, Manlio Perillo wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
In a project I'm working on, I use git, and I'm trying to follow the
versioning scheme used by the git project (since it is very pratical).
To summarize, git version is generated from the output of
On 17 Feb 2013 05:11, Chris Withers ch...@simplistix.co.uk wrote:
On 28/01/2013 18:21, Manlio Perillo wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
In a project I'm working on, I use git, and I'm trying to follow the
versioning scheme used by the git project (since it is very
On Sat, Feb 16, 2013 at 8:26 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 17 Feb 2013 05:11, Chris Withers ch...@simplistix.co.uk wrote:
On 28/01/2013 18:21, Manlio Perillo wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
In a project I'm working on, I use git, and
On Sun, Feb 17, 2013 at 11:56 AM, Daniel Holth dho...@gmail.com wrote:
I would think of a git^Wmercurial ID used as the last version component a
non-sorting string. It is never intended to actually break a tie between
two versions; if you do wind up using it to sort then you are in trouble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
In a project I'm working on, I use git, and I'm trying to follow the
versioning scheme used by the git project (since it is very pratical).
To summarize, git version is generated from the output of
git describe command, replacing the '-'
