From: Kristoffer Haugsbakk Date: Sun, 5 Apr 2026 10:32:00 +0000 (+0200) Subject: doc: gitcvs-migration: rephrase “man page” X-Git-Tag: v2.54.0-rc2~11^2 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=57177ad139c3d83116459c5a8ec323b8d2a050f4;p=thirdparty%2Fgit.git doc: gitcvs-migration: rephrase “man page” Let’s change the phrasing around the `linkgit` while we’re visiting this file (see previous commit[1]). We use the section syntax to refer to man pages, so writing “man page” next to it is a bit redundant. We can be more concise and just 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)”). † 1: Which also discusses why we do not change a similar phrasing in gittutorial(7) Signed-off-by: Kristoffer Haugsbakk Signed-off-by: Junio C Hamano --- diff --git a/Documentation/gitcvs-migration.adoc b/Documentation/gitcvs-migration.adoc index 2883834b71..905d08cd5f 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 list` 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