From: Alex Shi <seakeel@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
Jonathan Corbet <corbet@lwn.net>,
Hu Haowen <2023002089@link.tyut.edu.cn>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/zh: Fix Cc, Co-developed-by, and Signed-off-by tags
Date: Mon, 1 Apr 2024 09:40:11 +0800 [thread overview]
Message-ID: <339b5603-c09a-41de-af75-cf0f196a6310@gmail.com> (raw)
In-Reply-To: <22892a8ab5c17d7121ef5b85f7d18d8b1f41e434.1711715655.git.geert+renesas@glider.be>
On 3/29/24 8:35 PM, Geert Uytterhoeven wrote:
> The updates from commit ae67ee6c5e1d5b6a ("docs: fix Co-Developed-by
> docs") in v5.0 were never applied to the Chinese translations.
> In addition:
> - "Cc" used wrong case,
> - "Co-developed-by" lacked a dash,
> - "Signed-off-by" was misspelled.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
LGTM
Reviewed-by: Alex Shi <alexs@kernel.org>
> ---
> .../translations/zh_CN/process/submitting-patches.rst | 8 ++++----
> .../translations/zh_TW/process/submitting-patches.rst | 8 ++++----
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/process/submitting-patches.rst b/Documentation/translations/zh_CN/process/submitting-patches.rst
> index f8978f02057c164c..7864107e60a85c58 100644
> --- a/Documentation/translations/zh_CN/process/submitting-patches.rst
> +++ b/Documentation/translations/zh_CN/process/submitting-patches.rst
> @@ -333,10 +333,10 @@ Linus 和其他的内核开发者需要阅读和评论你提交的改动。对
> 未参与其开发。签署链应当反映补丁传播到维护者并最终传播到Linus所经过的 **真实**
> 路径,首个签署指明单个作者的主要作者身份。
>
> -何时使用Acked-by:,CC:,和Co-Developed by:
> +何时使用Acked-by:,Cc:,和Co-developed-by:
> ------------------------------------------
>
> -Singed-off-by: 标签表示签名者参与了补丁的开发,或者他/她在补丁的传递路径中。
> +Signed-off-by: 标签表示签名者参与了补丁的开发,或者他/她在补丁的传递路径中。
>
> 如果一个人没有直接参与补丁的准备或处理,但希望表示并记录他们对补丁的批准/赞成,
> 那么他们可以要求在补丁的变更日志中添加一个Acked-by:。
> @@ -358,8 +358,8 @@ Acked-by:不一定表示对整个补丁的确认。例如,如果一个补丁
> Co-developed-by: 声明补丁是由多个开发人员共同创建的;当几个人在一个补丁上工
> 作时,它用于给出共同作者(除了From:所给出的作者之外)。因为Co-developed-by:
> 表示作者身份,所以每个Co-developed-by:必须紧跟在相关合作作者的签署之后。标准
> -签署程序要求Singed-off-by:标签的顺序应尽可能反映补丁的时间历史,无论作者是通
> -过From:还是Co-developed-by:表明。值得注意的是,最后一个Singed-off-by:必须是
> +签署程序要求Signed-off-by:标签的顺序应尽可能反映补丁的时间历史,无论作者是通
> +过From:还是Co-developed-by:表明。值得注意的是,最后一个Signed-off-by:必须是
> 提交补丁的开发人员。
>
> 注意,如果From:作者也是电子邮件标题的From:行中列出的人,则From:标签是可选的。
> diff --git a/Documentation/translations/zh_TW/process/submitting-patches.rst b/Documentation/translations/zh_TW/process/submitting-patches.rst
> index 99fa0f2fe6f414e1..f12f2f193f855cfb 100644
> --- a/Documentation/translations/zh_TW/process/submitting-patches.rst
> +++ b/Documentation/translations/zh_TW/process/submitting-patches.rst
> @@ -334,10 +334,10 @@ Linus 和其他的內核開發者需要閱讀和評論你提交的改動。對
> 未參與其開發。簽署鏈應當反映補丁傳播到維護者並最終傳播到Linus所經過的 **真實**
> 路徑,首個簽署指明單個作者的主要作者身份。
>
> -何時使用Acked-by:,CC:,和Co-Developed by:
> +何時使用Acked-by:,Cc:,和Co-developed-by:
> ------------------------------------------
>
> -Singed-off-by: 標籤表示簽名者參與了補丁的開發,或者他/她在補丁的傳遞路徑中。
> +Signed-off-by: 標籤表示簽名者參與了補丁的開發,或者他/她在補丁的傳遞路徑中。
>
> 如果一個人沒有直接參與補丁的準備或處理,但希望表示並記錄他們對補丁的批准/贊成,
> 那麼他們可以要求在補丁的變更日誌中添加一個Acked-by:。
> @@ -359,8 +359,8 @@ Acked-by:不一定表示對整個補丁的確認。例如,如果一個補丁
> Co-developed-by: 聲明補丁是由多個開發人員共同創建的;當幾個人在一個補丁上工
> 作時,它用於給出共同作者(除了From:所給出的作者之外)。因爲Co-developed-by:
> 表示作者身份,所以每個Co-developed-by:必須緊跟在相關合作作者的簽署之後。標準
> -簽署程序要求Singed-off-by:標籤的順序應儘可能反映補丁的時間歷史,無論作者是通
> -過From:還是Co-developed-by:表明。值得注意的是,最後一個Singed-off-by:必須是
> +簽署程序要求Signed-off-by:標籤的順序應儘可能反映補丁的時間歷史,無論作者是通
> +過From:還是Co-developed-by:表明。值得注意的是,最後一個Signed-off-by:必須是
> 提交補丁的開發人員。
>
> 注意,如果From:作者也是電子郵件標題的From:行中列出的人,則From:標籤是可選的。
next prev parent reply other threads:[~2024-04-01 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 12:35 [PATCH] docs/zh: Fix Cc, Co-developed-by, and Signed-off-by tags Geert Uytterhoeven
2024-03-30 16:35 ` Hu Haowen
2024-04-01 1:40 ` Alex Shi [this message]
2024-04-02 12:04 ` Yanteng Si
2024-04-02 15:22 ` Jonathan Corbet
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=339b5603-c09a-41de-af75-cf0f196a6310@gmail.com \
--to=seakeel@gmail.com \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
/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