Git development
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>
Subject: Re: [PATCH 2/3] doc: gitcvs-migration: replace config -l and rephrase
Date: Tue, 31 Mar 2026 23:17:45 +0200	[thread overview]
Message-ID: <c93728fa-1d02-4b86-99e8-dcb5d8b74ac0@app.fastmail.com> (raw)
In-Reply-To: <xmqq5x6bzox5.fsf@gitster.g>

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!

  reply	other threads:[~2026-03-31 21:18 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 [this message]
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
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=c93728fa-1d02-4b86-99e8-dcb5d8b74ac0@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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