Re: Suggestion: drop 'g' in git-describe suffix

Han-Wen Nienhuys wrote:

Santi Béjar escreveu:

quoted

One problem I see with this scheme (either 'g', 'git' of '+') is that
it does not provide an increasing version number, even for
fast-forwarding commits. Then it is not useful as a package version
number (deb or rpm). I've already seen deb packages with
version+git20061010. One possibility could be to add the number of
commits between the tag and the commit as:

v1.4.3.3-git12g1e1f76e

to provide a weak ordering for fast-forwarding commits. What do you thing?

Is that number well defined if you merge branches in between?

I'd prefer

   v1.4.3.3+git-12-1e1f76e

or similar. Pasting together words without separator is bad for readability.

Or even IMVHO better:

    v1.4.3.3+12--1e1f76e

or something like that. v1.4.3.3+12 part meaning that v1.4.3.3 is 12 ancestor
in direct shortest direct line, or that v1.4.3.3+12 is 12 generations away
from v1.4.3.3.

Of course that is _costly_ to confitm that, and v1.4.3.3+12 might mean more
than one revision in presence of branching points, especially that there is
no equivalent of "first parent" to distinguish like in case of v1.4.3.3~12
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git