From: Andy Whitcroft <apw@shadowen.org>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: Suggestion: drop 'g' in git-describe suffix
Date: Thu, 02 Nov 2006 01:47:12 +0000 [thread overview]
Message-ID: <45494E20.1000503@shadowen.org> (raw)
In-Reply-To: <eibh94$t7n$1@sea.gmane.org>
Han-Wen Nienhuys wrote:
>
> hi,
>
> the convention to use a 'g' in the output of git-describe, eg.
>
> [lilydev@haring lilypond]$ git describe --abbrev=39
> lilypond_2_9_7-g47778d2297276484c861fc7536da13feb2d5fe8
>
>
> is confusing: the g is also a hex digit, and without reading the manual
> carefully, you'd think this is the commit g4777.
>
> Proposal: why not use
>
> tag#sha1
>
> or some other non-hex character.
g is not a hex digit, hex is 0-f ??
In current versions of git, this whole string is also a valid name for
the commit ie you can do the following:
git show lilypond_2_9_7-g47778d2297276484c861fc7536da13feb2d5fe8
-apw
next prev parent reply other threads:[~2006-11-02 1:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 1:23 Suggestion: drop 'g' in git-describe suffix Han-Wen Nienhuys
2006-11-02 1:47 ` Andy Whitcroft [this message]
2006-11-02 9:55 ` Han-Wen Nienhuys
2006-11-02 10:37 ` Andy Whitcroft
2006-11-02 10:53 ` Han-Wen Nienhuys
2006-11-02 10:59 ` Johannes Schindelin
2006-11-02 11:12 ` Santi Béjar
2006-11-02 11:21 ` Andy Whitcroft
2006-11-02 12:39 ` Santi Béjar
2006-11-02 13:52 ` Andy Whitcroft
2006-11-02 11:23 ` Han-Wen Nienhuys
2006-11-02 12:44 ` Santi Béjar
2006-11-02 14:07 ` Jakub Narebski
2006-11-02 14:48 ` Nicolas Vilz 'niv'
2006-11-02 15:01 ` Johannes Schindelin
2006-11-02 19:12 ` Nicolas Vilz 'niv'
2006-11-02 11:12 ` Andy Whitcroft
2006-11-02 11:03 ` Petr Baudis
2006-11-02 13:45 ` Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45494E20.1000503@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.