git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 2/2] repo: add --all to git-repo-info

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 21, 2025, 13:44 UTC
Message-ID
<xmqqms5kxtcq.fsf@gitster.g>
In-Reply-To
<aPcduvnjD0yphja2@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 12 quoted lines
>> +`info [--format=(keyvalue|nul)] [-z] [--all | <key>...]`::
> ...
> The synopsis now disagrees with the new behaviour, as it looks as if you
> can pick either "--all" or a set of keys. But we now support both at the
> same time.
>
> I know Junio mentioned this as one of the ways this may operate, and
> said that accepting both is the "most logical". I personally don't quite
> agree, and think that having it be either or is a bit saner. After all,
> what is the use case for listing specific keys twice? I cannot really
> see why one would ever want that. So I think we should accept either
> `--all` or keys, and die if they are used in combination.

Yup, unless we declare that the order of output is unspecified when "--all" is used (regardless of the presense of explicitly given keys), it would become awkweard to define the output behaviour. So I am OK to make the command behave as specified in the synopsis section.

Thanks.
Previous: Patrick SteinhardtNext: Lucas Seiki Oshiro
Message 5 of 6 in “repo: add --all to repo-info”
  1. 0/2 repo: add --all to repo-infoLucas Seiki Oshiro, Oct 20, 2025
  2. 1/2 repo: factor out field printing to dedicated functionLucas Seiki Oshiro, Oct 20, 2025
  3. 2/2 repo: add --all to git-repo-infoLucas Seiki Oshiro, Oct 20, 2025
  4. Patrick SteinhardtOct 21, 2025
  5. Junio C HamanoOct 21, 2025
  6. Lucas Seiki OshiroOct 24, 2025

Read the whole thread, see it on lore, or plain text.

$ 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.