From: Dongliang Mu <dzm91@hust.edu.cn>
To: Weijie Yuan <wy@wyuan.org>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] docs/zh_CN: update maintainer/configure-git.rst
Date: Mon, 16 Nov 2026 22:20:46 +0800 [thread overview]
Message-ID: <476202a2-26a7-4b6b-a7d5-ba8e586371bb@hust.edu.cn> (raw)
In-Reply-To: <20261109-configure-git-v3-0-d7807bb8e8c7@wyuan.org>
On 11/9/26 5:28 PM, Weijie Yuan wrote:
> Update the translation of two files:
>
> 1) maintainer/configure-git.rst
> 2) maintainer/pull-requests.rst
>
> I only update the first one in v1. However, I find a reference of
> pull-requests.rst in configure-git.rst is in English, while we've had a
> Chinese one. So, update both this time.
>
> Note that there're warm tips from checkpatch,
>
> checkpatch.pl: :6: WARNING: 'Link:' should be followed by a public http(s) link
> checkpatch.pl: Documentation/translations/zh_CN/maintainer/pull-requests.rst:118: WARNING: Do not use whitespace before Signed-off-by:
>
> .. which are caused by a 'Link:' in the commit message and a sample Sob
> trailer.
>
> ---
> Changes in v3:
> - Put "update to commit section" at the end of commit message in both.
> - Rebase to d48723711bae (Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux, 2026-11-06)
> Alex's docs-next HEAD now.
> - Link to v2: https://patch.msgid.link/20260905-configure-git-v2-0-ab194db8c6b9@wyuan.org
>
> Changes in v2:
> - Remove the SPDX identifier, see details and reasons in the thread of v1.
> - Add a new translation.
> - Link to v1: https://patch.msgid.link/20260823-configure-git-v1-1-3c65eefcc585@wyuan.org
>
> To: Alex Shi <alexs@kernel.org>
> To: Yanteng Si <si.yanteng@linux.dev>
> To: Dongliang Mu <dzm91@hust.edu.cn>
> To: Jonathan Corbet <corbet@lwn.net>
> To: Shuah Khan <skhan@linuxfoundation.org>
> To: Randy Dunlap <rdunlap@infradead.org>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> ---
> Weijie Yuan (2):
> docs/zh_CN: sync maintainer/configure-git with upstream
> docs/zh_CN: improve maintainer/pull-requests translation
>
> .../zh_CN/maintainer/configure-git.rst | 48 ++------
> .../zh_CN/maintainer/pull-requests.rst | 127 +++++++++++----------
> 2 files changed, 77 insertions(+), 98 deletions(-)
>
> Range-diff versus v2:
You need to tell your agent to forget about the range-diff.
Dongliang Mu
>
> 1: d292fa654b82 ! 1: a791cc884749 docs/zh_CN: sync maintainer/configure-git with upstream
> @@ Commit message
> adding Link trailers automatically with an applypatch-msg hook, because
> Link: trailers should only point to useful additional information.
>
> + Also point the pull-request reference to the Chinese translation.
> +
> Update the translation through commit 944df7a31452
> ("docs: update the guidance for Link: tags").
>
> - Also point the pull-request reference to the Chinese translation.
> -
> Signed-off-by: Weijie Yuan <wy@wyuan.org>
>
> ## Documentation/translations/zh_CN/maintainer/configure-git.rst ##
> 2: 9ed78fb91f42 ! 2: 2bec387ee1e3 docs/zh_CN: improve maintainer/pull-requests translation
> @@ Commit message
> After the last update to the Chinese translation, the English document
> removed the explicit section label, replaced the configure-git
> cross-reference with a direct path, and changed "tree for forever" to
> - "tree forever".
> + "tree forever". Remove the abandoned Chinese section label and point the
> + configure-git reference to the Chinese translation. Some of the existing
> + wording did not read very smoothly, so polish a few expressions and also
> + correct some Git terminology.
>
> Update the translation through commit 3a1b9c4d8edb
> ("docs: Remove redundant word "for"").
>
> - Remove the abandoned Chinese section label and point the configure-git
> - reference to the Chinese translation.
> -
> - Some of the existing wording did not read very smoothly, so polish a few
> - expressions. And also correct some Git terminology.
> -
> Signed-off-by: Weijie Yuan <wy@wyuan.org>
> - ---
> - I did make quite a few changes to make the reading more fluent. However,
> - to some extent, this might also be unnecessary. If you think there are
> - too many, I will remove the less essential ones. Thanks.
>
> ## Documentation/translations/zh_CN/maintainer/pull-requests.rst ##
> @@
>
> ---
> base-commit: d48723711bae9b8cdc56719c448ba42fef28cbee
> change-id: 20260823-configure-git-686aea09bf5b
next prev parent reply other threads:[~2026-11-16 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 9:28 Weijie Yuan
2026-11-09 9:28 ` [PATCH v3 1/2] docs/zh_CN: sync maintainer/configure-git with upstream Weijie Yuan
2026-11-16 14:44 ` Dongliang Mu
2026-11-09 9:28 ` [PATCH v3 2/2] docs/zh_CN: improve maintainer/pull-requests translation Weijie Yuan
2026-11-16 14:44 ` Dongliang Mu
2026-11-16 14:20 ` Dongliang Mu [this message]
2026-11-16 14:25 ` [PATCH v3 0/2] docs/zh_CN: update maintainer/configure-git.rst Weijie Yuan
2026-11-16 14:38 ` Weijie Yuan
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=476202a2-26a7-4b6b-a7d5-ba8e586371bb@hust.edu.cn \
--to=dzm91@hust.edu.cn \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=wy@wyuan.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
all inboxes | Powered by JetHome®