From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754579AbdKQKht (ORCPT ); Fri, 17 Nov 2017 05:37:49 -0500 Received: from mail.skyhub.de ([5.9.137.197]:34996 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750777AbdKQKhb (ORCPT ); Fri, 17 Nov 2017 05:37:31 -0500 Date: Fri, 17 Nov 2017 11:37:19 +0100 From: Borislav Petkov To: Greg Kroah-Hartman Cc: Jonathan Corbet , Thomas Gleixner , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Documentation/process: add Co-Developed-by: tag for patches with multiple authors Message-ID: <20171117103719.d7fht7txizqmb6o3@pd.tnic> References: <20171116132309.GA8449@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20171116132309.GA8449@kroah.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > Signed-off-by: Greg Kroah-Hartman > > > 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 -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.