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]

Message-ID: <20171117154633.59f657f9@lwn.net>
Date:   Fri, 17 Nov 2017 15:46:33 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>, 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 14:23:09 +0100
Greg Kroah-Hartman <gregkh@...uxfoundation.org> 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.

So this seems good, and I'm seeing no objections.  I can go ahead and
apply it and ship it upward.

That said, I do think that there should maybe be a mention in
submitting-patches.rst as well, since we have a fair amount of discussion
of patch tags there.  *Someday* we'll have nice organized documentation
that doesn't scatter this stuff around, but that's not this day...

Thanks,

jon