From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Mikael Magnusson <mikachu@gmail.com>,
Mark Burton <markb@ordern.com>
Subject: Re: [PATCH] Fix describe --tags --long so it does not segfault
Date: Wed, 02 Jul 2008 21:23:28 -0700 [thread overview]
Message-ID: <7vvdzn4mv3.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080703023245.GA31579@spearce.org> (Shawn O. Pearce's message of "Thu, 3 Jul 2008 02:32:45 +0000")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> If we match a lightweight (non-annotated tag) as the name to
> output and --long was requested we do not have a tag, nor do
> we have a tagged object to display. Instead we must use the
> object we were passed as input for the long format display.
>
> Reported-by: Mark Burton <markb@ordern.com>
> Backtraced-by: Mikael Magnusson <mikachu@gmail.com>
> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
> ---
>
> Thanks Mikael, the backtrace really made it easy to figure out
> what the breakage was here.
Thanks. I'll squash this in and apply to 'maint'. Perhaps 1.5.6.2
after the 4th holiday.
diff --git a/t/t6120-describe.sh b/t/t6120-describe.sh
index c6be259..2fb672c 100755
--- a/t/t6120-describe.sh
+++ b/t/t6120-describe.sh
@@ -139,4 +139,6 @@ check_describe "test1-lightweight-*" --tags --match="test1-*"
check_describe "test2-lightweight-*" --tags --match="test2-*"
+check_describe "test2-lightweight-*" --long --tags --match="test2-*" HEAD^
+
test_done
next prev parent reply other threads:[~2008-07-03 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 14:45 git describe --tags --long barfs on new tags? Mark Burton
2008-07-02 19:56 ` Mikael Magnusson
2008-07-03 2:32 ` [PATCH] Fix describe --tags --long so it does not segfault Shawn O. Pearce
2008-07-03 4:23 ` Junio C Hamano [this message]
2008-07-03 2:49 ` git describe --tags --long barfs on new tags? Abhijit Menon-Sen
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=7vvdzn4mv3.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=markb@ordern.com \
--cc=mikachu@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).