git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 10:37:31 +0000	[thread overview]
Message-ID: <4549CA6B.4090909@shadowen.org> (raw)
In-Reply-To: <4549C083.9060805@xs4all.nl>

Han-Wen Nienhuys wrote:
> Andy Whitcroft escreveu:
>>> or some other non-hex character.
>>
>> g is not a hex digit, hex is 0-f ??
>>
> 
> Yes of course; silly me. Still I think it would be clearer if it used a
> non-alphabet char, eg.
> 
>   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.  If you want the complete clean sha1
this is not the way to get it?


  reply	other threads:[~2006-11-02 10:38 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
2006-11-02  9:55   ` Han-Wen Nienhuys
2006-11-02 10:37     ` Andy Whitcroft [this message]
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=4549CA6B.4090909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).