From: Carl Worth <cworth@cworth.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Andy Whitcroft <apw@shadowen.org>, hanwen@xs4all.nl, git@vger.kernel.org
Subject: Re: Suggestion: drop 'g' in git-describe suffix
Date: Thu, 02 Nov 2006 05:45:03 -0800 [thread overview]
Message-ID: <8764dyvu74.wl%cworth@cworth.org> (raw)
In-Reply-To: <20061102110331.GJ20017@pasky.or.cz>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Thu, 2 Nov 2006 12:03:31 +0100, Petr Baudis wrote:
>
> Dear diary, on Thu, Nov 02, 2006 at 11:37:31AM CET, I got a letter
> where Andy Whitcroft <apw@shadowen.org> said that...
> > 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's rather to indicate that it is a sha1 at all.
Frankly, I've never understood the 'g' prefix at all. I don't use
git-describe much, but some people have sent me things with this 'g'
on the front and every time I've received that I was annoyed to find
the commit identifier they sent didn't work until I manually removed
it.
It's definitely never provided any useful semantic information to me.
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-11-02 13:45 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
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 [this message]
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=8764dyvu74.wl%cworth@cworth.org \
--to=cworth@cworth.org \
--cc=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--cc=pasky@suse.cz \
/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).