Linux Documentation
 help / color / mirror / Atom feed
From: Alex Shi <seakeel@gmail.com>
To: "Weijie Yuan" <wy@wyuan.org>,
	"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
	"Alex Shi" <alexs@kernel.org>,
	"Yanteng Si" <si.yanteng@linux.dev>,
	"Dongliang Mu" <dzm91@hust.edu.cn>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] docs/zh_CN: translate process/applying-patches.rst into Chinese
Date: Mon, 7 Sep 2026 13:39:27 +0800	[thread overview]
Message-ID: <15c96f0d-3b6e-4cd2-9d48-9b7a639cf3d5@gmail.com> (raw)
In-Reply-To: <20260817-apply-patches-v3-0-45e3bd2b1ccc@wyuan.org>

Applied, thanks!

On 2026/8/17 01:47, Weijie Yuan wrote:
> This series adds a Simplified Chinese translation of
> Documentation/process/applying-patches.rst.
> 
> The first patch adds the translation and includes it in the zh_CN process
> toctree.  Its :Original: field uses the original document path directly;
> no translation-specific reference label is introduced.
> 
> _Changes in v3_
> 
> The second patch updates existing zh_CN references to point to the new
> translation.  In ordinary paragraphs, the absolute Documentation/...rst
> path is used and is handled by automarkup.  The entry in process/howto.rst
> is a definition-list term, which automarkup does not process.  It therefore
> uses the named :doc: form as the minimal explicit-link exception, without
> reintroducing a cn_applying_patches label and using :ref:.
> 
> RFC:
> 
> I considered the two competing preferences for cross-references. Jon
> recommends using a plain absolute Documentation/...rst path, while
> another view (I found the discussion in 2021, so I added your email
> addresses, thanks.) is to avoid :doc: markup where automarkup can create
> the link automatically.  I follow both rules where they apply: the plain
> path is used in normal paragraphs.  However, this particular entry is a
> definition-list term, which automarkup does not process, so the plain
> path is rendered as text rather than a link.  The named :doc: form is
> therefore used only for this narrow exception, without adding a
> translation-specific label. (Seems to be a workaround)
> 
> I would welcome guidance on one stylistic point.  (Since I missed
> previous discussions)  The surrounding entries in this definition list
> use :ref:, while this new entry uses the named :doc: form because it
> links to a whole document without a translation-specific label. Does
> this look out of place here?  If so, I am happy to follow the preferred
> cross-reference style.
> 
> [Words are polished by LLM, but I think it's what I want to say]
> 
> Thanks!
> 
> Sorry Mauro, I don't know which address you'll prefer, so I add both.
> 
> ---
> Changes in v3:
> - Deal with the ref style, see above
> - Link to v2:https://patch.msgid.link/20260815-apply-patches-v2-0-3fdd873d31cc@wyuan.org
> 
> Changes in v2:
> - Merge first two patches into one.
> - Remove self-ref (.. _cn.rst) and changes ref style from 'ref' to
>    direct file name
> - Link to v1:https://patch.msgid.link/cover.1784289654.git.wy@wyuan.org
> 
> To: Mauro Carvalho Chehab<mchehab+huawei@kernel.org>
> To: Mauro Carvalho Chehab<mchehab@kernel.org>
> To: Nícolas F. R. A. Prado<nfraprado@collabora.com>
> 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>
> Cc:linux-doc@vger.kernel.org
> Cc:linux-kernel@vger.kernel.org
> 
> ---
> Weijie Yuan (2):
>        docs/zh_CN: add process/applying-patches Chinese translation
>        docs/zh_CN: link to Chinese applying-patches translation
> 
>   .../translations/zh_CN/admin-guide/README.rst      |   2 +-
>   .../zh_CN/process/applying-patches.rst             | 390 +++++++++++++++++++++
>   Documentation/translations/zh_CN/process/howto.rst |   2 +-
>   Documentation/translations/zh_CN/process/index.rst |   2 +-
>   4 files changed, 393 insertions(+), 3 deletions(-)
> 
> Range-diff versus v2:
> 
> 1:  596ec00ba7c5 = 1:  13da5addcb90 docs/zh_CN: add process/applying-patches Chinese translation
> 2:  b3a9c4893250 ! 2:  7c156c1d41b7 docs/zh_CN: link to Chinese applying-patches translation
>      @@ Documentation/translations/zh_CN/admin-guide/README.rst: Linux内核6.x版本 <h
>           并且希望跳转到6.0.3,那么在应用6.0.3补丁之前,必须首先撤销6.0.2补丁
>           (即patch -R)。更多关于这方面的内容,请阅读
>       -   :ref:`Documentation/process/applying-patches.rst <applying_patches>` 。
>      -+   :ref:`Documentation/translations/zh_CN/process/applying-patches.rst <cn_applying_patches>` 。
>      ++   Documentation/translations/zh_CN/process/applying-patches.rst 。
>        
>           或者,脚本 patch-kernel 可以用来自动化这个过程。它能确定当前内核版本并
>           应用找到的所有补丁::
>      @@ Documentation/translations/zh_CN/process/howto.rst: Linux内核代码中包含
>            的内容,可以查看这些文档。
>        
>       -  :ref:`Documentation/process/applying-patches.rst <applying_patches>`
>      -+  :ref:`Documentation/translations/zh_CN/process/applying-patches.rst <cn_applying_patches>`
>      ++  :doc:`Documentation/translations/zh_CN/process/applying-patches.rst <applying-patches>`
>            关于补丁是什么以及如何将它打在不同内核开发分支上的好介绍
>        
>        内核还拥有大量从代码自动生成或者从 ReStructuredText(ReST) 标记生成的文档,
> 
> ---
> base-commit: 1a0364f09c1311dad5ad1ccba7e169a412f6b547
> change-id: 20260815-apply-patches-601ad9b42f27
> 


      parent reply	other threads:[~2026-09-07  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 17:47 [PATCH v3 0/2] docs/zh_CN: translate process/applying-patches.rst into Chinese Weijie Yuan
2026-08-16 17:47 ` [PATCH v3 1/2] docs/zh_CN: add process/applying-patches Chinese translation Weijie Yuan
2026-08-16 17:47 ` [PATCH v3 2/2] docs/zh_CN: link to Chinese applying-patches translation Weijie Yuan
2026-09-07  5:39 ` Alex Shi [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=15c96f0d-3b6e-4cd2-9d48-9b7a639cf3d5@gmail.com \
    --to=seakeel@gmail.com \
    --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=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nfraprado@collabora.com \
    --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