linux-kernel - Re: [PATCH] Documentation/process: add Co-Developed-by: tag for patches with multiple authors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 17 Nov 2017 11:26:09 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation/process: add Co-Developed-by: tag for
 patches with multiple authors

On Thu, 16 Nov 2017, Greg Kroah-Hartman wrote:

> Sometimes a single patch is the result of multiple authors.  As git only
> can have one "author" of a patch, it is still good to properly give
> credit to the other developers of a commit.  To address this, document
> the "Co-Developed-by:" tag which can be used to show other authors of
> the patch.
> 
> Note, these other authors must also provide a Signed-off-by: tag as it
> is their work that is being submitted here.
> 
> Reported-by: Thomas Gleixner <tglx@...utronix.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>

> 
> diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst
> index 1b7728b19ea7..645fa9c7388a 100644
> --- a/Documentation/process/5.Posting.rst
> +++ b/Documentation/process/5.Posting.rst
> @@ -213,6 +213,11 @@ The tags in common use are:
>     which can be found in Documentation/process/submitting-patches.rst.  Code without a
>     proper signoff cannot be merged into the mainline.
>  
> + - 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.
> +
>   - Acked-by: indicates an agreement by another developer (often a
>     maintainer of the relevant code) that the patch is appropriate for
>     inclusion into the kernel.
>