[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Referring to revisions in the git future
From: |
Ivan Shmakov |
Subject: |
Re: Referring to revisions in the git future |
Date: |
Sat, 01 Nov 2014 12:47:57 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
>>>>> 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’.
>> 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?
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.
[…]
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
- Re: Referring to revisions in the git future., (continued)
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01
- Re: Referring to revisions in the git future., Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01
- Re: Referring to revisions in the git future., Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future,
Ivan Shmakov <=
- Re: Referring to revisions in the git future, Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future, Stephen J. Turnbull, 2014/11/01
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01