From: Weijie Yuan <wy@wyuan.org>
To: Nguyen Duc Thinh <ducthinh100812@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: process: Capitalize Git, Quilt, and Mercurial consistently
Date: Mon, 24 Aug 2026 20:02:19 +0800 [thread overview]
Message-ID: <aowyywsvZD_-rqSu@wyuan.org> (raw)
In-Reply-To: <20260824100050.12315-1-ducthinh100812@gmail.com>
On Mon, Aug 24, 2026 at 05:00:50PM +0700, Nguyen Duc Thinh wrote:
> Update various process documentation files to properly capitalize "Git",
> "Quilt", and "Mercurial" as proper nouns when referring to the source
> management tools themselves.
>
> Instances explicitly referring to literal command-line invocations
> (such as "git log" or "git bisect") have been left lowercase.
>
> Signed-off-by: Nguyen Duc Thinh <ducthinh100812@gmail.com>
> ---
> v2:
> - Fixed the extra spaces before ':' in the subject line.
Alright, thanks.
> - Reverted the accidental 'git switch' changes in submitting-patches.rst to keep the patch logically clean.
Really? But I see that is still here in your patch below.
That said, I suspect that some agents might simply prefer to do such
convenient things without informing the user. If you have used it, it
would be better to take a look at the corresponding policy, btw.
> - Regarding the scope: I did not fix every single instance across the entire documentation subsystem because the list is very long. I am primarily submitting this patch to gain hands-on experience with the Linux kernel contribution workflow.
Fair enough, welcome.
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index 7ae79452e..b6ca49437 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -866,7 +866,7 @@ automatically include the base tree information in your submission by
> using the ``--base`` flag. The easiest and most convenient way to use
> this option is with topical branches::
>
> - $ git checkout -t -b my-topical-branch master
> + $ git switch -t -c my-topical-branch master
> Branch 'my-topical-branch' set up to track local branch 'master'.
> Switched to a new branch 'my-topical-branch'
>
> @@ -882,7 +882,7 @@ notice that it will have the ``base-commit:`` trailer at the very
> bottom, which provides the reviewer and the CI tools enough information
> to properly perform ``git am`` without worrying about conflicts::
>
> - $ git checkout -b patch-review [base-commit-id]
> + $ git switch -c patch-review [base-commit-id]
> Switched to a new branch 'patch-review'
> $ git am patches.mbox
> Applying: First Commit
> --
> 2.50.1 (Apple Git-155)
Thanks.
prev parent reply other threads:[~2026-08-24 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 10:00 [PATCH v2] Documentation: process: Capitalize Git, Quilt, and Mercurial consistently Nguyen Duc Thinh
2026-08-24 12:02 ` Weijie Yuan [this message]
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=aowyywsvZD_-rqSu@wyuan.org \
--to=wy@wyuan.org \
--cc=corbet@lwn.net \
--cc=ducthinh100812@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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