Git development
 help / color / mirror / Atom feed
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 3/3] doc: replace the rest of git config --list with `list`
Date: Tue, 31 Mar 2026 14:10:35 -0700	[thread overview]
Message-ID: <xmqq1pgzzovo.fsf@gitster.g> (raw)
In-Reply-To: <doc_config_-l_the_rest.54d@msgid.xyz> (kristofferhaugsbakk@fastmail.com's message of "Tue, 31 Mar 2026 22:48:10 +0200")

kristofferhaugsbakk@fastmail.com writes:

> diff --git a/Documentation/gitprotocol-v2.adoc b/Documentation/gitprotocol-v2.adoc
> index c7db103299a..ec2562fb0a1 100644
> --- a/Documentation/gitprotocol-v2.adoc
> +++ b/Documentation/gitprotocol-v2.adoc
> @@ -659,7 +659,7 @@ use by the client, MUST indicate prerequisites (in any) with standard
>  applicable.
>  +
>  The advertised URI may alternatively contain a plaintext file that `git
> -config --list` would accept (with the `--file` option). The key-value
> +config list` would accept (with the `--file` option). The key-value
>  pairs in this list are in the `bundle.*` namespace (see
>  linkgit:git-config[1]).

OK.

> diff --git a/Documentation/gittutorial.adoc b/Documentation/gittutorial.adoc
> index f89ad30cf65..519b8d8be2c 100644
> --- a/Documentation/gittutorial.adoc
> +++ b/Documentation/gittutorial.adoc
> @@ -432,7 +432,7 @@ bob$ git config --get remote.origin.url
>  -------------------------------------
>  
>  (The complete configuration created by `git clone` is visible using
> -`git config -l`, and the linkgit:git-config[1] man page
> +`git config list`, and the linkgit:git-config[1] man page
>  explains the meaning of each option.)
>  
>  Git also keeps a pristine copy of Alice's `master` branch under the
> diff --git a/Documentation/technical/api-trace2.adoc b/Documentation/technical/api-trace2.adoc
> index cf493dae03f..918e517c2e6 100644
> --- a/Documentation/technical/api-trace2.adoc
> +++ b/Documentation/technical/api-trace2.adoc
> @@ -1253,7 +1253,7 @@ it.
>  $ git config --system color.ui never
>  $ git config --global color.ui always
>  $ git config --local color.ui auto
> -$ git config --list --show-scope | grep 'color.ui'
> +$ git config list --show-scope | grep 'color.ui'
>  system  color.ui=never
>  global  color.ui=always
>  local   color.ui=auto
> diff --git a/Documentation/user-manual.adoc b/Documentation/user-manual.adoc
> index 76969871176..3cd94c7afa1 100644
> --- a/Documentation/user-manual.adoc
> +++ b/Documentation/user-manual.adoc
> @@ -2865,7 +2865,7 @@ stored in Git configuration variables, which you can see using
>  linkgit:git-config[1]:
>  
>  -------------------------------------------------
> -$ git config -l
> +$ git config list
>  core.repositoryformatversion=0
>  core.filemode=true
>  core.logallrefupdates=true

Looking good.

Thanks.

  reply	other threads:[~2026-03-31 21:10 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
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 [this message]
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=xmqq1pgzzovo.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