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 <[email protected]> > > 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 :-)). How about the following: -- >From e28a8a940b219878d57add0d067a07764a6ef4a5 Mon Sep 17 00:00:00 2001 From: Borislav Petkov <[email protected]> Date: Thu, 25 Oct 2012 15:52:59 +0200 Subject: [PATCH] SubmittingPatches: Document multiple authorship Put down the way to express multiple authorship in writing for future reference. Signed-off-by: Borislav Petkov <[email protected]> --- Documentation/SubmittingPatches | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index c379a2a6949f..f61b1d8b6f9c 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -339,6 +339,16 @@ then you just add a line saying using your real name (sorry, no pseudonyms or anonymous contributions.) +In the case where two or more people work on one patch and contribute to +its final version, stating multiple authorship should be expressed by +adding the other co-authors of said patch to the tag chain like this: + + Based-on-work-by: Second Author <[email protected]> + Based-on-work-by: Third Author <[email protected]> + +Alternatively, the second, third, etc. authors can be credited as +copyright holders in the files being changed. + Some people also put extra tags at the end. They'll just be ignored for now, but you can do this to mark internal company procedures or just point out some special detail about the sign-off. -- 1.8.0 -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
