[1/2] docs: fix Co-Developed-by docs

Message ID 1544808928-20002-2-git-send-email-jorge.ramirez-ortiz@linaro.org
State Accepted
Commit ae67ee6c5e1d5b6acdb0d51fddde651834096d75
Headers show
Series
  • Fix Co-Developed-by
Related show

Commit Message

Jorge Ramirez-Ortiz Dec. 14, 2018, 5:35 p.m.
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@linaro.org>

---
 Documentation/process/submitting-patches.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.7.4

Comments

Himanshu Jha Dec. 14, 2018, 6:12 p.m. | #1
On Fri, Dec 14, 2018 at 06:35:27PM +0100, Jorge Ramirez-Ortiz wrote:
> 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@linaro.org>

> ---


Thanks. ACK!

Finally, the discussion converged at somepoint.

FYI, Cc Jonathan Cameron + IIO list.

>  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

> 


-- 
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology

Patch

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.