From: Michael J Gruber <git@drmicha.warpmail.net>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git checkout -b -t
Date: Tue, 02 Jun 2009 17:25:53 +0200 [thread overview]
Message-ID: <4A254481.3020104@drmicha.warpmail.net> (raw)
In-Reply-To: <43d8ce650906020749r36a0cceao20dc54d1446a6ea@mail.gmail.com>
John Tapsell venit, vidit, dixit 02.06.2009 16:49:
> Hey all,
>
> I've become the "guy to ask about git" in my company and people are
> always getting into a mess with git. So in turn I try to get git to
> be a more friendly. Today someone had a problem. Basically they had
> done:
>
> $ git checkout -t origin/mybranch
> fatal: git checkout: --track and --no-track require -b
>
> So they do exactly what it tells them:
> $ git checkout -b -t origin/mybranch
> Switched to a new branch "-t"
>
> doh
>
> How can we make this less easy for people to shoot themselves in the
> foot? The behavior of -t has changed recently iirc, so I think that
> problem has gone away?
git 1.6.1 and above contains DWIMery which, in the case above, would
automatically behave like
git checkout -t origin/mybranch -b mybranch
which complains in case 'mybranch' exists already, without pointing at
'-b', though. Do you think this creates a new type of head aches for
your patients?
>
> Also:
> $ git branch -D -t
>
> Doesn't work. I can see why, but it does make my life difficult :-D
>
> John
prev parent reply other threads:[~2009-06-02 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 14:49 git checkout -b -t John Tapsell
2009-06-02 15:04 ` Junio C Hamano
2009-06-02 15:05 ` Matthieu Moy
2009-06-02 15:25 ` Michael J Gruber [this message]
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=4A254481.3020104@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=johnflux@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 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.