From: Junio C Hamano <gitster@pobox.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git checkout -b -t
Date: Tue, 02 Jun 2009 08:04:10 -0700 [thread overview]
Message-ID: <7vd49mhe39.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <43d8ce650906020749r36a0cceao20dc54d1446a6ea@mail.gmail.com> (John Tapsell's message of "Tue\, 2 Jun 2009 15\:49\:53 +0100")
John Tapsell <johnflux@gmail.com> writes:
> $ 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?
(1) Explain things in terms of semantics, not in terms of "brainless
cut&paste" operations.
(2) Avoid telling them what to do in the error messages, instead why what
they did is an error.
E.g. "--track/--no-track does not make sense if you are not creating a new
branch" would be far less confusing in this particular case.
next prev parent reply other threads:[~2009-06-02 15:04 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 [this message]
2009-06-02 15:05 ` Matthieu Moy
2009-06-02 15:25 ` Michael J Gruber
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vd49mhe39.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).