While we're talking about 'git-describe': I always wondered what the '-g'
in front of the sha1 stands for when I issue 'git describe'. Is it for
'generation'
or what? Actually I'd appreciate if that '-g' would be dropped as it is of
no use but I also recognize that git-describe is one of the plumbing tools.
I'm just curious.
Dirk
Junio C Hamano schrieb:
Show 38 quoted lines
> Ian Hilt <ian.hilt@gmail.com> writes:
>
>
>> git-describe: Make description more readable.
>>
>
> Thanks, both. I think the above is meant to be on the Subject: line, and
> the text certainly is more readable.
>
>
>> Signed-off-by: Ian Hilt <ian.hilt@gmail.com>
>> ---
>> Documentation/git-describe.txt | 7 ++++---
>> 1 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/git-describe.txt b/Documentation/git-describe.txt
>> index d9aa2f2..69e1ab7 100644
>> --- a/Documentation/git-describe.txt
>> +++ b/Documentation/git-describe.txt
>> @@ -13,9 +13,10 @@ SYNOPSIS
>> DESCRIPTION
>> -----------
>> The command finds the most recent tag that is reachable from a
>> -commit, and if the commit itself is pointed at by the tag, shows
>> -the tag. Otherwise, it suffixes the tag name with the number of
>> -additional commits and the abbreviated object name of the commit.
>> +commit. If the tag points to the commit, then only the tag is
>> +shown. Otherwise, it suffixes the tag name with the number of
>> +additional commits on top of the tagged object and the
>> +abbreviated object name of the most recent commit.
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>