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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 16, 2017 at 02:23:09PM +0100, 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@xxxxxxxxxxxxx>
> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> 
> 
> 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.

Having a second or third author and specifying that fact keeps popping
up during review and people keep screwing up the SOB chains, trying to
express that. So yes, it is a good idea to have a special tag for this.

Acked-by: Borislav Petkov <bp@xxxxxxx>

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux