Re: [PATCH v3 16/36] doc txt & -h consistency: use "<options>", not "<options>..."

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 30, 2022, 21:43 UTC
Message-ID: <xmqqill48rob.fsf@gitster.g>
In-Reply-To: <patch-v3-16.36-db850539d2a-20220930T180415Z-avarab@gmail.com>

Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:

> It's arguably more correct to say "[<option>...]" than either of these
> forms, but the vast majority of our documentation uses the
> "[<options>]" form to indicate an arbitrary number of options, let's
> do the same in these cases, which were the odd ones out.

Yeah, I agree these should say [<option>...] to mean zero-or-more of them. It may be fine, as long as it is clear that we use [<options>] as a short-hand for it, though.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.