From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Teng Long <dyroneteng@gmail.com>,
git@vger.kernel.org, tenglong.tl@alibaba-inc.com
Subject: Re: [RFC PATCH v1 0/1] ls-remote: inconsistency from the order of args and opts
Date: Sat, 15 Jan 2022 02:02:15 +0100 [thread overview]
Message-ID: <220115.86czktrelu.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqr1996cw2.fsf@gitster.g>
On Fri, Jan 14 2022, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> But we should really be recommending use of -- or --end-of-options
>> whenever possible, as it can be hard to know in Git's CLI whether
>> options after args are accepted or not.
>
> Way before doing so, we should recommend the "options and then args"
> order. Users do not have to know which subcommands accepts options
> after args.
If you want to script git to do e.g.:
touch -- foo -r
git add foo -r
git rm foo -r
git status foo -r
git log foo -r
You do need to know that those won't work, if that "foo -r" is from
e.g. scripted arguments that those commands will accept or interpret
that -r as an argument.
Hence suggesting that the user just add "--" to resolve the ambiguity,
as gitcli already discusses.
next prev parent reply other threads:[~2022-01-15 1:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 4:24 [RFC PATCH v1 0/1] ls-remote: inconsistency from the order of args and opts Teng Long
2022-01-14 4:24 ` [RFC PATCH v1 1/1] ls-remote: Make the output independent of the order of opts and <remote> Teng Long
2022-01-14 5:47 ` [RFC PATCH v1 0/1] ls-remote: inconsistency from the order of args and opts Junio C Hamano
2022-01-14 6:27 ` Junio C Hamano
2022-01-14 6:42 ` Teng Long
2022-01-15 0:25 ` Junio C Hamano
2022-01-14 19:57 ` Ævar Arnfjörð Bjarmason
2022-01-14 20:42 ` Junio C Hamano
2022-01-14 20:57 ` Ævar Arnfjörð Bjarmason
2022-01-14 21:52 ` Junio C Hamano
2022-01-15 0:34 ` Ævar Arnfjörð Bjarmason
2022-01-15 1:01 ` Junio C Hamano
2022-01-14 21:12 ` brian m. carlson
2022-01-15 0:13 ` Ævar Arnfjörð Bjarmason
2022-01-15 0:50 ` Junio C Hamano
2022-01-15 1:02 ` Ævar Arnfjörð Bjarmason [this message]
2022-01-15 1:19 ` Junio C Hamano
2022-01-17 6:27 ` Teng Long
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=220115.86czktrelu.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
--cc=tenglong.tl@alibaba-inc.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).