From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>, git@vger.kernel.org
Subject: Re: bug? in checkout with ambiguous refnames
Date: Tue, 11 Jan 2011 14:20:20 -0500 [thread overview]
Message-ID: <20110111192020.GA15608@sigill.intra.peff.net> (raw)
In-Reply-To: <20110111065509.GG10094@sigill.intra.peff.net>
On Tue, Jan 11, 2011 at 01:55:09AM -0500, Jeff King wrote:
> On Fri, Jan 07, 2011 at 02:54:17PM -0500, Jeff King wrote:
>
> > +test_expect_success 'checkout reports switch to detached HEAD' '
> > + grep "Switched to branch" stderr &&
> > + ! grep "^HEAD is now at" stderr
>
> Junio, one minor fixup here. The test is correct, but the description
> should read "checkout reports switch to branch", not "...detached HEAD".
Hmm. One other thing to note on these ambiguity tests. Apparently we did
already have a test for this in t7201 (which should perhaps be renamed
into the t20* area with the other checkout tests), but it was passing.
The problem is that the current behavior is way more broken than just
"accidentally choose tag over branch". It actually writes the branch ref
into HEAD, but checks out the tree from the tag! The test in 7201 only
checks the former, but our new test checked the latter.
Probably we should be checking both, just to be sure (and yes, with your
patch it does the right thing):
diff --git a/t/t2019-checkout-amiguous-ref.sh b/t/t2019-checkout-amiguous-ref.sh
index e2b330b..606081b 100755
--- a/t/t2019-checkout-amiguous-ref.sh
+++ b/t/t2019-checkout-amiguous-ref.sh
@@ -22,6 +22,9 @@ test_expect_success 'checkout produces ambiguity warning' '
'
test_expect_success 'checkout chooses branch over tag' '
+ echo refs/heads/ambiguity >expect &&
+ git symbolic-ref HEAD >actual &&
+ test_cmp expect actual &&
echo branch >expect &&
test_cmp expect file
'
@@ -41,6 +44,9 @@ test_expect_success VAGUENESS_SUCCESS 'checkout produces ambiguity warning' '
'
test_expect_success VAGUENESS_SUCCESS 'checkout chooses branch over tag' '
+ echo refs/heads/vagueness >expect &&
+ git symbolic-ref HEAD >actual &&
+ test_cmp expect actual &&
echo branch >expect &&
test_cmp expect file
'
next prev parent reply other threads:[~2011-01-11 19:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 10:46 bug? in checkout with ambiguous refnames Uwe Kleine-König
2011-01-07 19:44 ` Junio C Hamano
2011-01-07 19:49 ` Jeff King
2011-01-07 19:54 ` Jeff King
2011-01-07 22:50 ` Junio C Hamano
2011-01-07 23:17 ` Junio C Hamano
2011-01-11 6:52 ` Jeff King
2011-01-11 17:02 ` Junio C Hamano
2011-01-11 18:02 ` Jeff King
2011-01-12 1:25 ` Jeff King
2011-01-12 9:07 ` Junio C Hamano
2011-01-12 17:27 ` Jeff King
2011-01-11 6:55 ` Jeff King
2011-01-11 19:20 ` Jeff King [this message]
2011-01-11 20:00 ` Jeff King
2011-01-08 20:40 ` Martin von Zweigbergk
2011-01-08 21:40 ` Jeff King
2011-01-09 2:43 ` Martin von Zweigbergk
2011-01-09 7:31 ` Junio C Hamano
2011-01-09 16:18 ` Martin von Zweigbergk
2011-01-12 9:11 ` Uwe Kleine-König
2011-01-12 17:46 ` Jeff King
2011-01-12 18:19 ` Uwe Kleine-König
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=20110111192020.GA15608@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).