From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Santi Béjar" <sbejar@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Teach git-describe --long to output always the long format
Date: Sun, 24 Feb 2008 19:08:08 -0800 [thread overview]
Message-ID: <7vwsotpwbr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080225023634.GK8410@spearce.org> (Shawn O. Pearce's message of "Sun, 24 Feb 2008 21:36:34 -0500")
"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.
next prev parent reply other threads:[~2008-02-25 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 14:46 [PATCH] Teach git-describe --long to output always the long format Santi Béjar
2008-02-25 2:36 ` Shawn O. Pearce
2008-02-25 3:08 ` Junio C Hamano [this message]
2008-02-25 8:34 ` Santi Béjar
2008-02-25 8:54 ` Junio C Hamano
2008-02-25 9:05 ` Santi Béjar
2008-02-25 20:11 ` Junio C Hamano
2008-02-25 20:51 ` Santi Béjar
2008-02-26 9:19 ` Junio C Hamano
2008-02-26 9:41 ` Santi Béjar
2008-02-25 8:50 ` Jakub Narebski
2008-02-25 9:43 ` Santi Béjar
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=7vwsotpwbr.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbejar@gmail.com \
--cc=spearce@spearce.org \
/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).