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

[PATCH 2/3] doc: gitcvs-migration: replace config -l and rephrase

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Mar 31, 2026, 20:48 UTC
Message-ID
<gitcvs_doc_link.54c@msgid.xyz>
In-Reply-To
<CV_doc_deprecation_config_--list.54a@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Replace `git config -l` with the subcommand `list` since `-l` is deprecated.

Let’s also change the phrasing around the `linkgit` while we’re visiting this file.

The Git documentation pages are both manual pages and HTML pages, and in any case we already use the section syntax to refer to them. So we don’t have to say “the _ man page”; we can be a bit more concise and only lean on the preposition “in”.

And in order to avoid this double “git”:
    see `git config list` in git-config(1) ...

We can rephrase to the subcommand, which is a typical pattern (config or option followed by “in git-command(1)”).

Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
    But this does make it more difficult to find back to later.
 Documentation/gitcvs-migration.adoc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/gitcvs-migration.adoc b/Documentation/gitcvs-migration.adoc
index 1cd1283d0f8..905d08cd5f9 100644
--- a/Documentation/gitcvs-migration.adoc
+++ b/Documentation/gitcvs-migration.adoc
@@ -49,8 +49,7 @@ them first before running git pull.
 ================================
 The 'pull' command knows where to get updates from because of certain
 configuration variables that were set by the first 'git clone'
-command; see `git config -l` and the linkgit:git-config[1] man
-page for details.
+command; see the subcommand `list` in linkgit:git-config[1] for details.
 ================================
 
 You can update the shared repository with your changes by first committing
-- 
2.53.0.32.gf6228eaf9cc
Previous: Kristoffer HaugsbakkNext: Junio C Hamano
Message 5 of 13 in “doc: replace mentions of deprecated git config --list”
  1. 0/3 doc: replace mentions of deprecated git config --listkristofferhaugsbakk@fastmail.com, Mar 31, 2026
  2. 1/3 doc: var: link -l to git config listkristofferhaugsbakk@fastmail.com, Mar 31, 2026
  3. Junio C HamanoMar 31, 2026
  4. Kristoffer HaugsbakkMar 31, 2026
  5. 2/3 doc: gitcvs-migration: replace config -l and rephrasekristofferhaugsbakk@fastmail.com, Mar 31, 2026
  6. Junio C HamanoMar 31, 2026
  7. Kristoffer HaugsbakkMar 31, 2026
  8. 3/3 doc: replace the rest of git config --list with `list`kristofferhaugsbakk@fastmail.com, Mar 31, 2026
  9. Junio C HamanoMar 31, 2026
  10. 0/2 doc: replace mentions of deprecated git config --listkristofferhaugsbakk@fastmail.com, Apr 5, 2026
  11. 1/2 doc: replace git config --list/-l with `list`kristofferhaugsbakk@fastmail.com, Apr 5, 2026
  12. 2/2 doc: gitcvs-migration: rephrase “man page”kristofferhaugsbakk@fastmail.com, Apr 5, 2026
  13. Junio C HamanoApr 6, 2026

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.