From: "Lars Hjemli" <hjemli@gmail.com>
To: "Jim Meyering" <jim@meyering.net>
Cc: "git list" <git@vger.kernel.org>
Subject: Re: why the 'g' prefix on the SHA1 in git-describe output?
Date: Sat, 3 Nov 2007 14:56:47 +0100 [thread overview]
Message-ID: <8c5c35580711030656h23d5910ah824de41a2cf4eafe@mail.gmail.com> (raw)
In-Reply-To: <871wb7a53d.fsf@rho.meyering.net>
On Nov 3, 2007 1:25 PM, Jim Meyering <jim@meyering.net> wrote:
> Can anyone tell me what motivated adding the 'g' prefix on the SHA1 in
> git-describe output?
I'm not sure what _motivated_ the 'g', but currently git-rev-parse
understands the output from git-describe _if_ the 'g' is present.
--
larsh
next prev parent reply other threads:[~2007-11-03 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 12:25 why the 'g' prefix on the SHA1 in git-describe output? Jim Meyering
2007-11-03 13:56 ` Lars Hjemli [this message]
2007-11-03 15:18 ` Andreas Ericsson
2007-11-03 16:10 ` Jim Meyering
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=8c5c35580711030656h23d5910ah824de41a2cf4eafe@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
/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).