Re: [PATCH] Teach git-describe --long to output always the long format

From: Santi Béjar <sbejar@gmail.com>
Date: Feb 25, 2008, 08:34 UTC
Message-ID: <8aa486160802250034ncdf20b6s13856ca8612bc2ea@mail.gmail.com>
In-Reply-To: <7vwsotpwbr.fsf@gitster.siamese.dyndns.org>

On Mon, Feb 25, 2008 at 4:08 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

> "Shawn O. Pearce" <spearce@spearce.org> writes:
>
>  >> +            else
>  >> +                    printf("%s-0-g%s\n", n->path,
>  >> +                            find_unique_abbrev(cmit->object.sha1, abbrev));
>  >
>  > Is this really that useful?  Where is having the tag and the commit
>  > SHA-1 both useful?
>
>  I had the same question.  The only place that I find this could
>  be useful is when you tag, build and install, and then find
>  glitches before pushing the results out and rewind, rebuild and
>  re-tag.  I unfortunately have this issue almost all the time.
>
>  But even then, I would probably not rely on this patch.
>

This can be usefull when more than one person can make "official" tags (or nobody), and then you have a uniqe idendifier with a descriptive name.

Santi