mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Yanteng Si <si.yanteng@linux.dev>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/16] docs/zh_TW: localize terminology and sync process/ documents
Date: Wed, 22 Jul 2026 23:09:49 +0800	[thread overview]
Message-ID: <amDdPZ4SqBNg1kBa@wyuan.org> (raw)
In-Reply-To: <20260721215542.98435-1-chenyou910331@gmail.com>

Sorry to be wordy,

In our zh_CN/how-to.rst, our template for commit message is:

---
docs/zh_CN: Add self-protection index Chinese translation

Translate .../security/self-protection.rst into Chinese.

Update the translation through commit b080e52110ea
("docs: update self-protection __ro_after_init status")
# 请执行 git log --oneline <您翻译的英文文档路径>,并替换上述内容

Signed-off-by: Yanteng Si <si.yanteng@linux.dev>
# 如果您前面的步骤正确执行,该行会自动显示,否则请检查 gitconfig 文件
---

So the ref for previous commit is wrapped, while in:

  https://docs.kernel.org/process/5.Posting.html#patch-formatting-and-changelogs

It asks do not wrap the ref of a certain commit, i.e. keep it as-is, in
the "Fixes:" trailer.

But our case is not about the "Fixes:" trailer, so my understanding is
that we should wrap the ref of previous commit in this series.

Hope there can be a consensus on this matter.

Thanks.

  parent reply	other threads:[~2026-07-22 15:09 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 21:55 Chen-Yu Yeh
2026-07-21 21:55 ` [PATCH 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst Chen-Yu Yeh
2026-07-22  5:56   ` Weijie Yuan
2026-07-22  8:48   ` Weijie Yuan
2026-07-22 13:32     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 02/16] docs/zh_TW: process: localize terminology in 1.Intro.rst Chen-Yu Yeh
2026-07-22  7:42   ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 03/16] docs/zh_TW: process: localize terminology in code-of-conduct-interpretation.rst Chen-Yu Yeh
2026-07-21 21:55 ` [PATCH 04/16] docs/zh_TW: process: localize terminology in license-rules.rst Chen-Yu Yeh
2026-07-22 11:35   ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 05/16] docs/zh_TW: process: localize terminology in email-clients.rst Chen-Yu Yeh
2026-07-22 11:35   ` Weijie Yuan
2026-07-24  6:48     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 06/16] docs/zh_TW: process: localize terminology in programming-language.rst Chen-Yu Yeh
2026-07-22 14:51   ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 07/16] docs/zh_TW: process: localize terminology in coding-style.rst Chen-Yu Yeh
2026-07-22 14:48   ` Weijie Yuan
2026-07-24  6:38     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 08/16] docs/zh_TW: process: localize terminology in stable-kernel-rules.rst Chen-Yu Yeh
2026-07-21 21:55 ` [PATCH 09/16] docs/zh_TW: process: localize terminology in 5.Posting.rst Chen-Yu Yeh
2026-07-23  7:02   ` Weijie Yuan
2026-07-24  6:40     ` 葉宸佑
2026-07-24 14:11       ` Weijie Yuan
2026-07-25  0:46         ` 葉宸佑
2026-07-21 21:55 ` [PATCH 10/16] docs/zh_TW: process: localize terminology in 2.Process.rst Chen-Yu Yeh
2026-07-23  6:30   ` Weijie Yuan
2026-07-24  6:41     ` 葉宸佑
2026-07-24 13:57       ` Weijie Yuan
2026-07-26  8:56     ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 11/16] docs/zh_TW: process: localize terminology in howto.rst Chen-Yu Yeh
2026-07-23 10:53   ` Weijie Yuan
2026-07-24  6:41     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 12/16] docs/zh_TW: process: localize terminology in embargoed-hardware-issues.rst Chen-Yu Yeh
2026-07-23 12:43   ` Weijie Yuan
2026-07-24  6:42     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 13/16] docs/zh_TW: process: localize terminology in submitting-patches.rst Chen-Yu Yeh
2026-07-24 11:06   ` Weijie Yuan
2026-07-25  0:36     ` 葉宸佑
2026-08-05  7:00       ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 14/16] docs/zh_TW: process: localize terminology in 8.Conclusion.rst Chen-Yu Yeh
2026-07-24 12:08   ` Weijie Yuan
2026-07-25  0:43     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 15/16] docs/zh_TW: process: localize terminology in index.rst Chen-Yu Yeh
2026-07-24 12:27   ` Weijie Yuan
2026-07-25  0:44     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 16/16] docs/zh_TW: Add a glossary for Traditional Chinese translations Chen-Yu Yeh
2026-07-24 12:56   ` Weijie Yuan
2026-07-25  0:41     ` 葉宸佑
2026-07-22 15:09 ` Weijie Yuan [this message]
2026-07-24  6:36   ` [PATCH 00/16] docs/zh_TW: localize terminology and sync process/ documents 葉宸佑

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=amDdPZ4SqBNg1kBa@wyuan.org \
    --to=wy@wyuan.org \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=alexs@kernel.org \
    --cc=chenyou910331@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    /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

Powered by JetHome