From: Clemens Buchacher <drizzd@aon.at>
To: git@vger.kernel.org
Cc: Peter Rabbitson <ribasushi@cpan.org>
Subject: DWIM "git checkout frotz" to "git checkout -b frotz origin/frotz"
Date: Sat, 5 Jun 2010 13:09:30 +0200 [thread overview]
Message-ID: <20100605110930.GA10526@localhost> (raw)
Hi,
Peter and I just stumbled on the following interpretations of the
checkout command.
git checkout origin/frotz -> detaches HEAD
git checkout -t origin/frotz -> git checkout -b frotz origin/frotz
git checkout frotz -> git checkout -b frotz origin/frotz
git checkout -t frotz -> fatal: Missing branch name
I was surprised by the third one, which I was expecting to fail.
Apparently it's a DWIM feature introduced in commit 70c9ac2f. I
doubt that is what the user was trying to do if they ran that
command. If anything, this behavior will serve to confuse them.
I think git checkout -t <remote>/<branch> is short enough for
creating a new tracking branch. For something even shorter, we can
create an alias. But I'd prefer to keep the already complex
checkout command a little simpler.
Regards,
Clemens
next reply other threads:[~2010-06-05 11:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 11:09 Clemens Buchacher [this message]
2010-06-05 13:29 ` DWIM "git checkout frotz" to "git checkout -b frotz origin/frotz" Sverre Rabbelier
2010-06-05 13:58 ` Clemens Buchacher
2010-06-05 14:03 ` Sverre Rabbelier
2010-06-05 15:02 ` Clemens Buchacher
2010-06-05 18:23 ` Nicolas Pitre
2010-06-06 16:18 ` Jeff King
2010-06-06 16:55 ` Clemens Buchacher
2010-06-06 16:59 ` Jacob Helwig
2010-06-06 17:32 ` Clemens Buchacher
2010-06-06 17:34 ` Sverre Rabbelier
2010-06-06 21:26 ` Jacob Helwig
2010-06-07 18:29 ` Clemens Buchacher
2010-06-07 20:11 ` Jan Krüger
2010-06-07 21:12 ` Clemens Buchacher
2010-06-06 18:34 ` Johan Herland
2010-06-06 16:18 ` Matthieu Moy
2010-06-06 16:46 ` Clemens Buchacher
2010-06-07 6:41 ` Miles Bader
2010-06-07 18:54 ` Clemens Buchacher
2010-06-07 19:17 ` Matthieu Moy
2010-06-07 19:32 ` Clemens Buchacher
2010-06-07 19:52 ` Bruce Stephens
2010-06-08 8:07 ` Michael J Gruber
2010-06-08 8:18 ` demerphq
2010-06-08 8:37 ` Michael J Gruber
2010-06-08 0:25 ` Miles Bader
2010-06-08 7:29 ` Clemens Buchacher
2010-06-08 7:47 ` demerphq
2010-06-08 13:04 ` Matthieu Moy
2010-06-08 7:52 ` Miles Bader
2010-06-08 7:52 ` Jeff King
2010-06-08 18:13 ` Clemens Buchacher
2010-06-07 7:53 ` Paolo Bonzini
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=20100605110930.GA10526@localhost \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=ribasushi@cpan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.