From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Clemens Buchacher <drizzd@aon.at>, Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Peter Rabbitson <ribasushi@cpan.org>
Subject: Re: DWIM "git checkout frotz" to "git checkout -b frotz origin/frotz"
Date: Sun, 06 Jun 2010 20:34:19 +0200 [thread overview]
Message-ID: <201006062034.19471.johan@herland.net> (raw)
In-Reply-To: <20100606165554.GB10104@localhost>
On Sunday 06 June 2010, Clemens Buchacher wrote:
> On Sun, Jun 06, 2010 at 12:18:05PM -0400, Jeff King wrote:
> > Moreover, the burden for arguing against it is a little higher. It is
> > no longer "I think this is a bad idea" but "I think this is a bad
> > idea, and it is so bad that it is worth changing behavior that users
> > may have become accustomed to".
>
> I argue that people are more likely to be surprised and confused by
> this feature rather than being accustomed to it already. I am also
> waiting to hear from someone who actively uses this feature.
I use this feature all the time, and find it very nice and useful.
Moreover, at $DAYJOB, we have a lot of Git newbies (many of them still can't
properly juggle remote branches. remote-tracking branches, and local
branches with tracking info). They mostly work on local topic branches that
tracks corresponding shared topic branches in a central repo. For them,
switching to one of these topic branches is simply a matter of 'git checkout
<branchname>', without having to care (or know) if you've already created
the local branch or not. In this case, Git really does the Right Thing (tm)
for us.
In several cases this DWIMmery has prompted people to update from an old Git
version, just to get this feature.
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2010-06-06 18:36 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
2010-06-07 21:12 ` Clemens Buchacher
2010-06-06 18:34 ` Johan Herland [this message]
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=201006062034.19471.johan@herland.net \
--to=johan@herland.net \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--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).