linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Daniel J Blueman <daniel@numascale-asia.com>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	H Peter Anvin <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Multiple patch authors (was: Re: [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains)
Date: Thu, 25 Oct 2012 15:59:48 +0200	[thread overview]
Message-ID: <20121025135948.GA308@x1.osrc.amd.com> (raw)
In-Reply-To: <20121025115654.GA27611@gmail.com>

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@alien8.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 :-)).

How about the following:

--
>From e28a8a940b219878d57add0d067a07764a6ef4a5 Mon Sep 17 00:00:00 2001
From: Borislav Petkov <bp@alien8.de>
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 <bp@alien8.de>
---
 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 <second.author@example.org>
+	Based-on-work-by: Third Author  <third.author@example.org>
+
+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.

  reply	other threads:[~2012-10-25 13:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25  8:32 [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains Daniel J Blueman
2012-10-25 11:03 ` Borislav Petkov
2012-10-25 11:56   ` Ingo Molnar
2012-10-25 13:59     ` Borislav Petkov [this message]
2012-10-25 14:32       ` Multiple patch authors H. Peter Anvin
2012-10-25 14:36         ` Borislav Petkov
2012-10-25 14:41           ` H. Peter Anvin
2012-10-25 15:23             ` Borislav Petkov
2012-10-29  6:17   ` [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains Daniel J Blueman
2012-10-29  8:54     ` Daniel J Blueman
2012-10-29 10:32       ` Borislav Petkov
2012-10-31  5:23         ` Daniel J Blueman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121025135948.GA308@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@numascale-asia.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).