From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Guillaume Pages <guillaume.pages@ensimag•grenoble-inp.fr>
Cc: git@vger•kernel.org,
Remi Lespinet <remi.lespinet@ensimag•grenoble-inp.fr>,
Remi Galan <remi.galan-alfonso@ensimag•grenoble-inp.fr>,
Antoine Delaite <antoine.delaite@ensimag•grenoble-inp.fr>,
Louis-Alexandre Stuber
<louis--alexandre.stuber@ensimag•grenoble-inp.fr>
Subject: Re: [BUG] potential error in parsing git checkout options?
Date: Fri, 29 May 2015 14:23:02 +0200 [thread overview]
Message-ID: <vpqiobb7eu1.fsf@anie.imag.fr> (raw)
In-Reply-To: <854038739.144343.1432895421483.JavaMail.zimbra@ensimag.grenoble-inp.fr> (Guillaume Pages's message of "Fri, 29 May 2015 12:30:21 +0200 (CEST)")
Guillaume Pages <guillaume.pages@ensimag•grenoble-inp.fr> writes:
> Git version : 2.4.1.652.g8fd8657
>
> When we run git checkout -babar, we would expect an error message like
> "unknown switch 'a' " and we get "Switched to a new branch 'abar'".
Yes, the option-parser accepts sticked form (-bbranch) and unsticked (-b
branch). This is the convention with most Unix commands (try "grep -e
foo" Vs "grep -efoo").
It gets more confusing for "git -amend" Vs "git --amend", which got a
special-case to avoid confusion (strictly speaking, it should have been
equivalent to "git commit -a -m end").
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2015-05-29 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <156258182.144342.1432895411512.JavaMail.zimbra@ensimag.grenoble-inp.fr>
2015-05-29 10:30 ` [BUG] potential error in parsing git checkout options? Guillaume Pages
2015-05-29 12:23 ` Matthieu Moy [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=vpqiobb7eu1.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=antoine.delaite@ensimag$(echo .)grenoble-inp.fr \
--cc=git@vger$(echo .)kernel.org \
--cc=guillaume.pages@ensimag$(echo .)grenoble-inp.fr \
--cc=louis--alexandre.stuber@ensimag$(echo .)grenoble-inp.fr \
--cc=remi.galan-alfonso@ensimag$(echo .)grenoble-inp.fr \
--cc=remi.lespinet@ensimag$(echo .)grenoble-inp.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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