From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: 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: Fri, 14 Jan 2022 13:52:11 -0800 [thread overview]
Message-ID: <xmqqo84e9e9g.fsf@gitster.g> (raw)
In-Reply-To: <220114.86y23iqbbk.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Fri, 14 Jan 2022 21:57:33 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>>> But when GNU came around its option parser was generally happy to accept
>>> options and args in either order. E.g. these both work with GNU
>>> coreutils, but the latter will fail on FreeBSD and various other
>>> capital-U UNIX-es:
>>>
>>> touch foo; rm -v foo
>>> touch foo; rm foo -v
>
> This is only an approximate list, but:
Don't waste your time on this, and instead spend on something more
useful. What I gave wrt gitcli.txt in an earlier message is final.
next prev parent reply other threads:[~2022-01-14 21:52 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo84e9e9g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--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.
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.