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] [day] [month] [year] [list]
Message-ID: <CAGXu5jKFM2JHc2H1UTrTQ8kBpZcp_FvyPc1Oea0aHCPwE=MKoQ@mail.gmail.com>
Date:   Tue, 16 Jan 2018 14:43:57 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Jonathan Corbet <corbet@....net>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation/process: add Co-Developed-by: tag for
 patches with multiple authors

On Thu, Nov 16, 2017 at 5:23 AM, 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.
>
> Reported-by: Thomas Gleixner <tglx@...utronix.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

I see no uses of this tag yet, and I'd like to get it right. If patch
v1 was written by author A, then heavily modified and sent by author B
to produce patch v2, what should the resulting states of git-author,
and tag order be? I'm assuming it should be:

git-author: B
...
Signed-off-by: A
Co-Developed-by: A
Signed-off-by: B

It's not clear to me if git-author should instead be A, and/or
Co-Developed-by should be B...

Thanks!

-Kees

-- 
Kees Cook
Pixel Security

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ