linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linux.alibaba.com>
To: alex.shi@linux.alibaba.com, harryxiyou@gmail.com, corbet@lwn.net,
	leoyang.li@nxp.com, linux-doc@vger.kernel.org
Cc: Tom Levy <tomlevy93@gmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 42/42] docs/zh_CN: update co-developed-by info after English version
Date: Wed, 27 Mar 2019 21:01:48 +0800	[thread overview]
Message-ID: <20190327130148.3258-43-alex.shi@linux.alibaba.com> (raw)
In-Reply-To: <20190327130148.3258-1-alex.shi@linux.alibaba.com>

commit 24a2bb90741b ("docs: Clarify the usage and sign-off requirements for Co-developed-by")
give more info of co-developed-by tag usage. update Chinese docs to
follow it.

Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Harry Wei <harryxiyou@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Tom Levy <tomlevy93@gmail.com>
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
 .../translations/zh_CN/process/5.Posting.rst  |  7 ++--
 .../zh_CN/process/submitting-patches.rst      | 35 +++++++++++++++++--
 2 files changed, 37 insertions(+), 5 deletions(-)

diff --git a/Documentation/translations/zh_CN/process/5.Posting.rst b/Documentation/translations/zh_CN/process/5.Posting.rst
index a8a6a7dacd7f..b3a5a352d4d6 100644
--- a/Documentation/translations/zh_CN/process/5.Posting.rst
+++ b/Documentation/translations/zh_CN/process/5.Posting.rst
@@ -159,8 +159,11 @@ bug搜寻人员想知道补丁是否负责他们正在追查的问题,想知
    :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
    中找到,如果没有适当的签字,则不能合并到主线中。
 
- - Co-developed-by: 声明补丁也是由另一个开发人员和原始作者一起创建的。当多
-   个人在一个补丁上工作时,这很有用。注意,此人也需要在补丁中有一个签名行。
+ - Co-developed-by: 声明补丁是由多个开发人员共同创建的;当几个人在一个补丁上
+   工作时,它用于将属性赋予共同作者(除了 From: 所赋予的作者之外)。因为
+   Co-developed-by: 表示作者身份,所以每个共同开发人, 必须紧跟在相关合作作者
+   的签名之后。具体内容和示例可以在以下文件中找到
+   :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
 
  - Acked-by: 表示另一个开发人员(通常是相关代码的维护人员)同意补丁适合包含
    在内核中。
diff --git a/Documentation/translations/zh_CN/process/submitting-patches.rst b/Documentation/translations/zh_CN/process/submitting-patches.rst
index 93239649fb71..850c295a07a0 100644
--- a/Documentation/translations/zh_CN/process/submitting-patches.rst
+++ b/Documentation/translations/zh_CN/process/submitting-patches.rst
@@ -427,8 +427,37 @@ Acked-by:不一定表示对整个补丁的确认。例如,如果一个补丁
 这是唯一一个标签,它可以在没有被它命名的人显式操作的情况下添加,但它应该表明
 这个人是在补丁上抄送的。讨论中包含了潜在利益相关方。
 
-Co-developed-by: 声明补丁也是由另一个开发人员和原始作者一起创建的。当多个人
-在一个补丁上工作时,这很有用。注意,此人也需要在补丁中有一个 Signed-off-by:
+Co-developed-by: 声明补丁是由多个开发人员共同创建的;当几个人在一个补丁上工
+作时,它用于将属性赋予共同作者(除了 From: 所赋予的作者之外)。因为
+Co-developed-by: 表示作者身份,所以每个共同开发人:必须紧跟在相关合作作者的
+签名之后。标准的签核程序要求:标记的签核顺序应尽可能反映补丁的时间历史,而不
+管作者是通过 From :还是由 Co-developed-by: 共同开发的。值得注意的是,最后一
+个签字人:必须始终是提交补丁的开发人员。
+
+注意,当作者也是电子邮件标题“发件人:”行中列出的人时,“From: ” 标记是可选的。
+
+作者提交的补丁程序示例::
+
+	<changelog>
+
+	Co-developed-by: First Co-Author <first@coauthor.example.org>
+	Signed-off-by: First Co-Author <first@coauthor.example.org>
+	Co-developed-by: Second Co-Author <second@coauthor.example.org>
+	Signed-off-by: Second Co-Author <second@coauthor.example.org>
+	Signed-off-by: From Author <from@author.example.org>
+
+合作开发者提交的补丁示例::
+
+	From: From Author <from@author.example.org>
+
+	<changelog>
+
+	Co-developed-by: Random Co-Author <random@coauthor.example.org>
+	Signed-off-by: Random Co-Author <random@coauthor.example.org>
+	Signed-off-by: From Author <from@author.example.org>
+	Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
+	Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
+
 
 13)使用报告人:、测试人:、审核人:、建议人:、修复人:
 --------------------------------------------------------
@@ -538,7 +567,7 @@ e-mail 标题中的“一句话概述”扼要的描述 e-mail 中的补丁。
     Subject: [PATCHv2 001/207] x86: fix eflags tracking
 
 "From" 行是信体里的最上面一行,具有如下格式:
-        From: Original Author <author@example.com>
+        From: Patch Author <author@example.com>
 
 "From" 行指明在永久改动日志里,谁会被确认为作者。如果没有 "From" 行,那
 么邮件头里的 "From: " 行会被用来决定改动日志中的作者。
-- 
2.19.1.856.g8858448bb


      parent reply	other threads:[~2019-03-27 13:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190327130148.3258-1-alex.shi@linux.alibaba.com>
2019-03-27 13:01 ` [PATCH 01/42] docs/zh_CN: translate development-process into Chinese Alex Shi
2019-03-27 13:01 ` [PATCH 02/42] docs/zh_CN: add disclaimer and translator info in development-process Alex Shi
2019-03-27 13:01 ` [PATCH 03/42] docs/zh_CN: link development-process into process index Alex Shi
2019-03-27 13:01 ` [PATCH 04/42] docs/zh_CN: add Chinese 1.Intro file Alex Shi
2019-03-27 13:01 ` [PATCH 05/42] docs/zh_CN: add disclaimer and translator info into 1.Intro Alex Shi
2019-03-27 13:01 ` [PATCH 06/42] docs/zh_CN: add 2.Process.rst for development-process Alex Shi
2019-03-27 13:01 ` [PATCH 07/42] docs/zh_CN: add disclaimer and translator info in 2.Process Alex Shi
2019-03-27 13:01 ` [PATCH 08/42] docs/zh_CN: translate 3.Early-stage of development process Alex Shi
2019-03-27 13:01 ` [PATCH 09/42] docs/zh_CN: add disclaimer/translator info in 3.Early-stage Alex Shi
2019-03-27 13:01 ` [PATCH 10/42] docs/zh_CN: add 4.Coding.rst Alex Shi
2019-03-27 13:01 ` [PATCH 11/42] docs/zh_CN: add disclaimer and translator info in 4.Coding Alex Shi
2019-03-27 13:01 ` [PATCH 12/42] docs/zh_CN: add 5.Posting.rst into development-process Alex Shi
2019-03-27 13:01 ` [PATCH 13/42] docs/zh_CN: add disclaimer and translator info in 5.Posting Alex Shi
2019-03-27 13:01 ` [PATCH 14/42] docs/zh_CN: add the 6th doc 6.Followthrought.rst Alex Shi
2019-03-27 13:01 ` [PATCH 15/42] docs/zh_CN: add disclaimer and translator info in 6.Followthrough Alex Shi
2019-03-27 13:01 ` [PATCH 16/42] docs/zh_CN: translate 7.AdvanceTopics.rst Alex Shi
2019-03-27 13:01 ` [PATCH 17/42] docs/zh_CN: add disclaimer and translator info in 7.Advancedtopics Alex Shi
2019-03-27 13:01 ` [PATCH 18/42] docs/zh_CN: add 8.Conclusion.rst in development-process Alex Shi
2019-03-27 13:01 ` [PATCH 19/42] docs/zh_CN: add disclaimer and translator info in 8.Conclusion Alex Shi
2019-03-27 13:01 ` [PATCH 20/42] docs/zh_CN: add license-rules Chinese translation Alex Shi
2019-03-27 13:01 ` [PATCH 21/42] docs/zh_CN: fix links failure in license-rules Alex Shi
2019-03-27 13:01 ` [PATCH 22/42] docs/zh_CN: include Chinese translation header for license-rules Alex Shi
2019-03-27 13:01 ` [PATCH 23/42] docs/zh_CN: link the license-rules file into process index Alex Shi
2019-03-27 13:01 ` [PATCH 24/42] docs/zh_CN: add submit-checklist file Alex Shi
2019-03-27 13:01 ` [PATCH 25/42] docs/zh_CN: add disclaimer and transtlator info in submit-checklist Alex Shi
2019-03-27 13:01 ` [PATCH 26/42] docs/zh_CN: link the submit-checklist into process/index Alex Shi
2019-03-27 13:01 ` [PATCH 27/42] docs/zh_CN: add CoC doc Alex Shi
2019-03-27 13:01 ` [PATCH 28/42] docs/zh_CN: add disclaimer and translator info in CoC Alex Shi
2019-03-27 13:01 ` [PATCH 29/42] docs/zh_CN: link the CoC into process/index Alex Shi
2019-03-27 13:01 ` [PATCH 30/42] docs/zh_CN: add CoC interpretation Alex Shi
2019-03-27 13:01 ` [PATCH 31/42] docs/zh_CN: add disclaim and translator into CoC interp Alex Shi
2019-03-27 13:01 ` [PATCH 32/42] docs/zh_CN: link CoC interpretation into index Alex Shi
2019-03-27 13:01 ` [PATCH 33/42] docs/zh_CN: fix link issue in howto.rst Alex Shi
2019-03-27 13:01 ` [PATCH 34/42] docs/zh_CN: update howto.rst to latest version Alex Shi
2019-03-27 13:01 ` [PATCH 35/42] docs/zh_CN: update translator info and comments in howto Alex Shi
2019-03-27 13:01 ` [PATCH 36/42] docs/zh_CN: redirect license-rules to Chinese doc Alex Shi
2019-03-27 13:01 ` [PATCH 37/42] docs/zh_CN: redirect howto.rst link to Chinese version Alex Shi
2019-03-27 13:01 ` [PATCH 38/42] docs/zh_CN: update to latest submitting-patches.rst Alex Shi
2019-03-27 13:01 ` [PATCH 39/42] docs/zh_CN: update translator info in submitting-patches Alex Shi
2019-03-27 13:01 ` [PATCH 40/42] docs/zh_CN: redirect the submitting-patches to Chinese doc Alex Shi
2019-03-27 13:01 ` [PATCH 41/42] docs/zh_CN: redirect submit-checklist Alex Shi
2019-03-27 13:01 ` 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=20190327130148.3258-43-alex.shi@linux.alibaba.com \
    --to=alex.shi@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=harryxiyou@gmail.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomlevy93@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).