[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1544808928-20002-2-git-send-email-jorge.ramirez-ortiz@linaro.org>
Date: Fri, 14 Dec 2018 18:35:27 +0100
From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@...aro.org>
To: jorge.ramirez-ortiz@...aro.org, joe@...ches.com,
gregkh@...uxfoundation.org, himanshujha199640@...il.com
Cc: apw@...onical.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, niklas.cassel@...aro.org,
corbet@....net, linux-doc@...r.kernel.org
Subject: [PATCH 1/2] docs: fix Co-Developed-by docs
The accepted terminology will be Co-developed-by therefore losing the
capital letter from now on.
Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@...aro.org>
---
Documentation/process/submitting-patches.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index c091710..30dc00a 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -510,7 +510,7 @@ tracking your trees, and to people trying to troubleshoot bugs in your
tree.
-12) When to use Acked-by:, Cc:, and Co-Developed-by:
+12) When to use Acked-by:, Cc:, and Co-developed-by:
-------------------------------------------------------
The Signed-off-by: tag indicates that the signer was involved in the
@@ -543,7 +543,7 @@ person it names - but it should indicate that this person was copied on the
patch. This tag documents that potentially interested parties
have been included in the discussion.
-A Co-Developed-by: states that the patch was also created by another developer
+A Co-developed-by: states that the patch was also created by another developer
along with the original author. This is useful at times when multiple people
work on a single patch. Note, this person also needs to have a Signed-off-by:
line in the patch as well.
--
2.7.4
Powered by blists - more mailing lists