From 57177ad139c3d83116459c5a8ec323b8d2a050f4 Mon Sep 17 00:00:00 2001 From: Kristoffer Haugsbakk Date: Sun, 5 Apr 2026 12:32:00 +0200 Subject: [PATCH] =?utf8?q?doc:=20gitcvs-migration:=20rephrase=20=E2=80=9Cm?= =?utf8?q?an=20page=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit 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 --- 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 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 -- 2.52.0