From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Dannier Castro L <danniercl@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
Jonathan Nieder <jrnieder@gmail.com>,
Brandon Williams <bmwill@google.com>
Subject: Re: [PATCH 1/3] checkout.c: add strict usage of -- before file_path
Date: Mon, 14 May 2018 10:51:15 +0900 [thread overview]
Message-ID: <xmqqsh6vc8do.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8DZ1QvjO+JdbB76TOLtB2wp4Ya+CgsTyD1oz2Y+ZdKdYQ@mail.gmail.com> (Duy Nguyen's message of "Sun, 13 May 2018 08:03:24 +0200")
Duy Nguyen <pclouds@gmail.com> writes:
>
> I would like an option to revert back to current behavior. I'm not a
> new user. I know what I'm doing. Please don't make me type more.
I can guarantee that nobody will stay a newbie. They either become
more proficient and aware of what they are doing without having to
think, at which point they start feeling the same way as you are.
Or they leave the Git ecosystem and move to better things ;-)
> And '--" is not completely useless. If you have <file> and <branch>
> with the same name, you have to give "--" to to tell git what the
> first argument means.
Correct.
We _could_ do better than the corrent code, though, when we happen
to have a file called 'master'. "git checkout master master" cannot
mean anything other than "I want to make the index and the working
tree copies of 'master' file to match what is recorded on the master
branch", but I think we do require "git checkout master -- master"
disambiguation.
next prev parent reply other threads:[~2018-05-14 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 2:23 [PATCH 1/3] checkout.c: add strict usage of -- before file_path Dannier Castro L
2018-05-13 2:23 ` [PATCH 2/3] test: update tests for strict usage of -- checkout Dannier Castro L
2018-05-13 2:23 ` [PATCH 3/3] doc: update doc " Dannier Castro L
2018-05-13 6:03 ` [PATCH 1/3] checkout.c: add strict usage of -- before file_path Duy Nguyen
2018-05-13 19:11 ` Dannier Castro L
2018-05-13 20:18 ` SZEDER Gábor
2018-05-13 23:06 ` Philip Oakley
2018-05-14 1:51 ` Junio C Hamano [this message]
2018-05-13 21:02 ` Kevin Daudt
2018-05-14 14:52 ` Duy Nguyen
2018-05-14 15:43 ` Duy Nguyen
[not found] <9e3a36eea5d34dc2941560b96046dc27@BPMBX2013-01.univ-lyon1.fr>
2018-05-13 16:52 ` Matthieu Moy
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=xmqqsh6vc8do.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=bmwill@google.com \
--cc=danniercl@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pclouds@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).