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

From: Nicolas Vilz 'niv' <niv@iaglans.de>
Date: Nov 2, 2006, 14:48 UTC
Message-ID: <454A0538.9000104@iaglans.de>
In-Reply-To: <8aa486160611020312v42047716t6a13e6fa16eeae8@mail.gmail.com>

Santi Béjar wrote:

Show 27 quoted lines

> On 11/2/06, Han-Wen Nienhuys <hanwen@xs4all.nl> wrote:
>> Andy Whitcroft escreveu:
>> > Han-Wen Nienhuys wrote:
>> >>
>> >>   tag+sha1
>> >>
>> >> to separate the tag and the committish.
>> >
>> > Well there is a non-alphabet character in there, a minus (-).  The g
>> > prefix on the sha1 _fragment_ it to indicate that it is in fact a
>> > truncated sha1, not a complete one.
> 
> I think it is there to indicate it is a git commit sha1.
> 
>>
>> is this policy documented somewhere?  None of the tools understand it.
>>
>> [lilydev@haring git]$ git describe
>> v1.4.3.3-g1e1f76e
>> [lilydev@haring git]$ git show g1e1f76e
>> fatal: ambiguous argument 'g1e1f76e': unknown revision or path not in
>> the working tree.
>> Use '--' to separate paths from revisions
>>
> 
> Use the complete output of describe:
> $ git show v1.4.3.3-g1e1f76e

this one doesn't work for me in my repository.

$ git-describe release_1_22_v0.7-g85eb121

$ git show release_1_22_v0.7-g85eb121 fatal: ambiguous argument 'release_1_22_v0.7-g85eb121': unknown revision or path not in the working tree. Use '--' to separate paths from revisions

> or the abbrev sha1:
> $ git show 1e1f76e

this one works with my repository

$ git show 85eb121

i use git version 1.4.2.rc2.g2686c

(that was next branch of git one or two days ago or so..)

it would be great to let the full output of git describe work as well.

Sincerly