From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Thu, 05 Feb 2026 17:38:44 GMT
Subject: Re: [PATCH 06/11] docs: add design doc for config-batch
Message-ID: <1702a6b0-78a0-49e8-b3e0-a112c251c9ed@app.fastmail.com>
In-Reply-To: <014e959cf4a4e19afe6becdb155f49d0f96739f8.1770214803.git.gitgitgadget@gmail.com>

On Wed, Feb 4, 2026, at 15:19, Derrick Stolee via GitGitGadget wrote:
>[snip]
> +Current commands
> +----------------
> +
> +See the documentation in linkgit::config-batch[1] for the latest set of

s/linkgit::config-batch[1]/linkgit:git-config-batch[1]/

> +available commands and their protocols.
> +
> +Future commands
> +---------------
> +
> +The following modes of `git config` are not currently available as
> commands
> +in `git config-batch`, but are planned for future integration:
> +
> +`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?

> +
> +`git config set [--<scope>] <key> <value>`::
> +	It will be desirable to set a config key at a given scope as a
> +	single value, replacing the current value at that scope, if it
> +	exists and is a single value. A `set` command could satisfy this
> +	purpose.
> +
> +`git config set --all [<value-pattern>|--fixed-value=<fixedvalue>]
> <key> <value>`::
> +	When replacing multiple values, it may be necessary to have a
> different
> +	output describing the places those values were set, so it may need to
> +	be implemented via a `set-all` command to differentiate from a `set`
> +	command.
> +
> +`git config unset <key>`::
> +
> +`git config unset --all [<value-pattern>|--fixed-value=<fixedvalue>]
> <key>`::
> +
> +`git config get --all --rexexp <key-pattern> [<value-options>]`::
> +
> +`--replace-all` option::
> +
> +`--type=<type>` option::
> --
> gitgitgadget