From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
git@vger.kernel.org
Subject: Re: bug? in checkout with ambiguous refnames
Date: Wed, 12 Jan 2011 01:07:51 -0800 [thread overview]
Message-ID: <7vd3o232xk.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110112012515.GA30856@sigill.intra.peff.net> (Jeff King's message of "Tue\, 11 Jan 2011 20\:25\:15 -0500")
Jeff King <peff@peff.net> writes:
> I'm not sure. And to be honest I don't really care, because I think
> people with ambiguous refs are little bit crazy anyway (after all, in
> the current code it simply calls die()). But I think there is some
> argument to be made that due to tracking, start_point is not _just_
> a regular ref. We do care about its branchiness.
I do not really care either myself, and if
git branch --track foo heads/ambiguity
git branch --track foo tags/ambiguity
allows the user to differentiate between the branch and the tag, it would
be more than sufficient.
next prev parent reply other threads:[~2011-01-12 9:08 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 [this message]
2011-01-12 17:27 ` Jeff King
2011-01-11 6:55 ` Jeff King
2011-01-11 19:20 ` Jeff King
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=7vd3o232xk.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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).