Re: Referring to revisions in the git future

[Alan Mackenzie]

Hello, Ivan.

On Sat, Nov 01, 2014 at 12:47:57PM +0000, Ivan Shmakov wrote:
> >>>>> Alan Mackenzie <address@hidden> writes:
> >>>>> On Sat, Nov 01, 2014 at 12:57:13PM +0100, David Kastrup wrote:

>  >> address@hidden:/usr/local/tmp/git$ git describe 
>  >> v2.1.0-rc2-3-g67de23d

>  > Maybe I'm blind, but I can't see anything like a sequential version
>  > number in that string.

>       It comes in-between the tag name (v2.1.0-rc2) and the Git
>       revision proper (g67de23d), prefixed with a ‘g’.

Ah, it's the "3".

>  >> Nobody uses it in Email communication because there are no
>  >> sufficient upsides to it.

>  > Is it of any use for anything?  Can you use it as input to a git
>  > command, for example?

By which I meant the sequential version number.  Clearly "3" is not going
to do anything at all.

>       The part of that string after the last ‘g’ (that is: 67de23d) is
>       an abbreviated Git revision hash, which could be used with just
>       about any Git command.

So, in other words, you might as well just use the "67de23d" rather than
typing in the whole lot.

> -- 
> FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A

-- 
Alan Mackenzie (Nuremberg, Germany).