From: Weijie Yuan <kernel@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: 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>, Weijie Yuan <wy@wyuan.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/9] docs/zh_CN: align translation paths and update guides
Date: Wed, 28 Oct 2026 16:12:34 +0800 [thread overview]
Message-ID: <auGucr4smrSp9g5l@wyuan.org> (raw)
In-Reply-To: <20261028034134.4144660-1-dzm91@hust.edu.cn>
On Wed, Oct 28, 2026 at 11:41:25AM +0800, Dongliang Mu wrote:
> Several Chinese translations are no longer at the same relative paths as
> their English originals, and some Original fields are stale. This series
> moves the translations to matching paths, adjusts their indexes, and
> removes stale Original fields. It also updates selected translations to
> newer English commits.
>
> v1->v2:
> - Drop the unused top-level readme_zh label from the translated
> admin-guide README.
Hmm, so why still keeping these labels here?
[2/9] .. _zh_applying_patches:
[4/9] .. _process_index_zh:
[5/9] .. _magicnumbers_zh:
Thanks.
> Dongliang Mu (9):
> docs/zh_CN: update admin-guide/index.rst translation
> docs/zh_CN: update admin-guide/README.rst translation
> docs/zh_CN: add media administrator guide translations
> docs/zh_CN: reorganize process debugging guides
> docs/zh_CN: update magic-number to match upstream
> docs/zh_CN: reorganize media driver API translations
> docs/zh_CN: move GFS2 translations into filesystems/gfs2
> docs/zh_CN: update networking/xfrm/xfrm_proc.rst translation
> docs/zh_CN: remove stale Original fields from SCSI and IPE
> translations
next prev parent reply other threads:[~2026-10-28 8:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 3:41 [PATCH v2 0/9] docs/zh_CN: align translation paths and update guides Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 1/9] docs/zh_CN: update admin-guide/index.rst translation Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 2/9] docs/zh_CN: update admin-guide/README.rst translation Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 3/9] docs/zh_CN: add media administrator guide translations Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 4/9] docs/zh_CN: reorganize process debugging guides Dongliang Mu
2026-10-28 8:04 ` Weijie Yuan
2026-10-28 8:06 ` Weijie Yuan
2026-10-29 12:23 ` Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 5/9] docs/zh_CN: update magic-number to match upstream Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 6/9] docs/zh_CN: reorganize media driver API translations Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 7/9] docs/zh_CN: move GFS2 translations into filesystems/gfs2 Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 8/9] docs/zh_CN: update networking/xfrm/xfrm_proc.rst translation Dongliang Mu
2026-10-28 3:41 ` [PATCH v2 9/9] docs/zh_CN: remove stale Original fields from SCSI and IPE translations Dongliang Mu
2026-10-28 8:12 ` Weijie Yuan [this message]
2026-10-28 12:37 ` [PATCH v2 0/9] docs/zh_CN: align translation paths and update guides Dongliang Mu
2026-10-30 3:29 ` Weijie Yuan
2026-10-30 5:49 ` Dongliang Mu
2026-10-30 5:55 ` 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=auGucr4smrSp9g5l@wyuan.org \
--to=kernel@wyuan.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.