From: Kristoffer Haugsbakk Date: Tue, 31 Mar 2026 21:17:45 GMT Subject: Re: [PATCH 2/3] doc: gitcvs-migration: replace config -l and rephrase Message-ID: In-Reply-To: On Tue, Mar 31, 2026, at 23:09, Junio C Hamano wrote: > kristofferhaugsbakk@fastmail.com writes: > >> 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. >> ================================ > > OK. In this step, "while at it" change is also sensible, unlike the > one in [1/3]. It wouldn't have been time-wasting if you sifted the > patches into "genuinely, move away from -l and to 'list'" changes > and everything else, as the former we do not have to think, while > the latter we do. Okay. That’s great. I am far to the side of separating changes in terms of personal inclination. I’ll split the -l/--list change and the While At Its. Thanks!