Re: [RFC PATCH v1 0/1] ls-remote: inconsistency from the order of args and opts

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 15, 2022, 00:25 UTC
Message-ID: <xmqqwnj17slr.fsf@gitster.g>
In-Reply-To: <CADMgQSQC4T+MBgbFROy0cmB8FFk=EgikPfErwpMbduaFvEebDA@mail.gmail.com>

Teng Long <dyroneteng@gmail.com> writes:

Show 12 quoted lines

> On Fri, Jan 14, 2022 at 1:47 PM Junio C Hamano <gitster@pobox.com> wrote:
>
>> Apparently, it is not a common knowledge at least for you (and
>> probably others).  Perhaps we should add a paragraph to the cli help
>> and explicitly mention "options first and then args", before we go
>> on to say "among args, revs first and then pathspecs".
>
> It's much clearer now, thanks for the detailed answer.
>
> Another question, if I want to follow your advice and add a short
> paragraph in git CLI document, should this patch continue in the
> current RFC patchset or launch a new patchset?

If I were you, I would retract the ls-remote topic and create a brand new topic that is about clarifying/enhancing the gitcli.txt file, which has nothing to do with ls-remote, because the command line option/argument convention is not specific to a single command.