From: Junio C Hamano <gitster@pobox.com>
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>,
ps@pks.im
Subject: Re: [PATCH 1/3] doc: var: link -l to git config list
Date: Tue, 31 Mar 2026 14:12:12 -0700 [thread overview]
Message-ID: <xmqqv7ebya8j.fsf@gitster.g> (raw)
In-Reply-To: <doc_var_no_config_-l.54b@msgid.xyz> (kristofferhaugsbakk@fastmail.com's message of "Tue, 31 Mar 2026 22:48:08 +0200")
kristofferhaugsbakk@fastmail.com writes:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> The option `-l` is deprecated and links to `git config -l` as the
> replacement—which is also deprecated. Break the deprecation chain by
> linking to `git config list`, the command which has superseded `git
> config -l`.
>
> Also promote this part from a parenthetical to a warning admonition.
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
> ---
> Documentation/git-var.adoc | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-var.adoc b/Documentation/git-var.adoc
> index b606c2d6499..98f4dc1a479 100644
> --- a/Documentation/git-var.adoc
> +++ b/Documentation/git-var.adoc
> @@ -21,8 +21,9 @@ OPTIONS
> `-l`::
> Display the logical variables. In addition, all the
> variables of the Git configuration file .git/config are listed
> - as well. (However, the configuration variables listing functionality
> - is deprecated in favor of `git config -l`.)
> + as well.
> ++
> +WARNING: Deprecated in favor of `git config list`.
This changes the meaning, and I am afraid in a bad way.
Use if "git var -l" to ask values of configuration variables is
deprecated, as we would encourage use of "git config [-l | list]".
"git var -l" is and will stay to be the way to ask about logical
variables.
The new text, unlike the original, does not limit the deprecation
only for asking about configuration variables.
The logical variables are called logical because their values are
synthesized from information taken from different places (e.g., you
might not have user.name configured but may have GIT_AUTHOR_NAME
environment variable set and exported or your name configured
correctly in GECOS field. We can ask what the value of
GIT_AUTHOR_IDENT is, without knowing where that value comes from,
and the source might be outside the usual Git configuration
subsystem, which makes it "logical").
I'd prefer to see this step just stick to `git config -l` => `git config list`
rewrite without the separate WARNING: style change.
next prev parent reply other threads:[~2026-03-31 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 20:48 [PATCH 0/3] doc: replace mentions of deprecated git config --list kristofferhaugsbakk
2026-03-31 20:48 ` [PATCH 1/3] doc: var: link -l to git config list kristofferhaugsbakk
2026-03-31 21:12 ` Junio C Hamano [this message]
2026-03-31 21:14 ` Kristoffer Haugsbakk
2026-03-31 20:48 ` [PATCH 2/3] doc: gitcvs-migration: replace config -l and rephrase kristofferhaugsbakk
2026-03-31 21:09 ` Junio C Hamano
2026-03-31 21:17 ` Kristoffer Haugsbakk
2026-03-31 20:48 ` [PATCH 3/3] doc: replace the rest of git config --list with `list` kristofferhaugsbakk
2026-03-31 21:10 ` Junio C Hamano
2026-04-05 10:31 ` [PATCH v2 0/2] doc: replace mentions of deprecated git config --list kristofferhaugsbakk
2026-04-05 10:31 ` [PATCH v2 1/2] doc: replace git config --list/-l with `list` kristofferhaugsbakk
2026-04-05 10:32 ` [PATCH v2 2/2] doc: gitcvs-migration: rephrase “man page” kristofferhaugsbakk
2026-04-06 17:04 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqv7ebya8j.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox