From: Matt McCutchen <matt@mattmccutchen.net>
To: git <git@vger.kernel.org>
Subject: "git checkout: --track and --no-track require -b" check accidentally resurrected?
Date: Sat, 18 Oct 2008 20:54:12 -0400 [thread overview]
Message-ID: <1224377652.19061.12.camel@mattlaptop2.local> (raw)
Merge commit 9ba929ed resurrected the following two-line check, which
was removed in the first parent and unchanged in the second:
if (!opts.new_branch && (opts.track != git_branch_track))
die("git checkout: --track and --no-track require -b");
Is this intentional? Does it make a difference?
(I noticed this while carefully examining 9ba929ed to find out why "git
merge" stopped honoring merge.conflictstyle. Ironically, I hit this bug
again during the examination.)
Matt
next reply other threads:[~2008-10-19 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 0:54 Matt McCutchen [this message]
2008-10-19 22:15 ` "git checkout: --track and --no-track require -b" check accidentally resurrected? Junio C Hamano
2008-10-19 22:52 ` Is XDL_MERGE_ZEALOUS too zealous (or maybe not zealous enough)? Junio C Hamano
2008-10-20 3:42 ` Matt McCutchen
2008-10-20 16:17 ` Johannes Schindelin
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=1224377652.19061.12.camel@mattlaptop2.local \
--to=matt@mattmccutchen.net \
--cc=git@vger.kernel.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).