Re: [PATCH 06/11] docs: add design doc for config-batch

From: Derrick Stolee <stolee@gmail.com>
Date: Feb 10, 2026, 04:22 UTC
Message-ID: <a9c39434-c179-491f-87fb-52b1c2705790@gmail.com>
In-Reply-To: <1702a6b0-78a0-49e8-b3e0-a112c251c9ed@app.fastmail.com>

On 2/5/2026 12:38 PM, Kristoffer Haugsbakk wrote:

> On Wed, Feb 4, 2026, at 15:19, Derrick Stolee via GitGitGadget wrote:

Show 6 quoted lines

>> +`git config list [--<scope>]`::
>> +	Getting all values, regardless of config key, would require a
>> +	multi-valued output similar to the `help` command. This tool will
>> +	likely assume advanced options such as `--show-origin`.
> 
> What does it mean to assume options?

I mean that since we expect to have the output parsed by tools, then
we will probably want the maximum amount of information by default.
Maybe --show-origin isn't as helpful as --show-scope.
 
Thanks,
-Stolee

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