linux-kernel - Re: Multiple patch 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: <50894D84.9030203@zytor.com>
Date:	Thu, 25 Oct 2012 07:32:36 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>,
	Daniel J Blueman <daniel@...ascale-asia.com>,
	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Multiple patch authors

On 10/25/2012 06:59 AM, Borislav Petkov wrote:
> On Thu, Oct 25, 2012 at 01:56:54PM +0200, Ingo Molnar wrote:
>> No, SOBs are to document patch forwarding. Co-authorship can be
>> expressed a number of ways, such as:
>>
>> Based-on-patch-from: Borislav Petkov <bp@...en8.de>
>>
>> and/or by adding you as a copyright holder to one of the files.
>
> Ok, let's hold this down in writing for future reference and in case I
> forget (which will happen, most probably :-)).
>

I have also used:

Originally-by:

... for a patch originally written by one person but then extensively 
reworked to the point of not really being the same work.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/