git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Krüger" <jk@jk.gs>
To: Clemens Buchacher <drizzd@aon.at>
Cc: Jacob Helwig <jacob.helwig@gmail.com>, Jeff King <peff@peff.net>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	git@vger.kernel.org, Peter Rabbitson <ribasushi@cpan.org>
Subject: Re: DWIM "git checkout frotz" to "git checkout -b frotz  origin/frotz"
Date: Mon, 7 Jun 2010 22:11:34 +0200	[thread overview]
Message-ID: <20100607221134.002ae81a@jk.gs> (raw)
In-Reply-To: <20100607182956.GA17343@localhost>

Clemens Buchacher <drizzd@aon.at> wrote:

> > Other than "unexpected success", how is the DWIM behavior confusing,
> > given that it says exactly what it's doing when the DWIM behavior is
> > invoked?  I'm still not clear what the confusion you're referring to
> > is on this one.
> 
> I am telling git to checkout a branch. Instead it creates a branch.
> That is what is confusing to me. Until I found the commit that
> introduced it, I was sure it must be a bug.

I usually see the opposite kind of confusion on #git: someone cloned a
repository and wants to work on one of the branches. After all, we tell
everyone that clone copies all the history.

So they type "git checkout <that branch>"... and they get a weird
error (what's a pathspec, anyway?). OMGWTFBBQ! Not knowing what's going
on, they drop by in #git and hear they need to type something much less
straightforward than "git checkout <that branch>". They don't really
know why, so they probably assume it's because git is just so damn
complicated and overengineered.

I have yet to see any newish users complain about the new syntax, by the
way. You don't qualify, sorry. ;)

  reply	other threads:[~2010-06-07 20:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 11:09 DWIM "git checkout frotz" to "git checkout -b frotz origin/frotz" Clemens Buchacher
2010-06-05 13:29 ` 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 [this message]
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=20100607221134.002ae81a@jk.gs \
    --to=jk@jk.gs \
    --cc=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=jacob.helwig@gmail.com \
    --cc=peff@peff.net \
    --cc=ribasushi@cpan.org \
    --cc=srabbelier@gmail.com \
    /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).