From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
Daniel J Blueman <daniel@numascale-asia.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Multiple patch authors
Date: Thu, 25 Oct 2012 07:41:18 -0700 [thread overview]
Message-ID: <50894F8E.9060706@zytor.com> (raw)
In-Reply-To: <20121025143626.GD308@x1.osrc.amd.com>
On 10/25/2012 07:36 AM, Borislav Petkov wrote:
> On Thu, Oct 25, 2012 at 07:32:36AM -0700, H. Peter Anvin wrote:
>> 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.
>
> Yes, whatever wording we agree upon for the tag, it should be as general
> text as possible so that it fits the majority of multiple authorship
> cases.
>
Not necessarily. It is actually better to have more specific tags for
different situations.
There is a reason why tip-bot accepts any tag ending in -by: ...
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-10-25 14:41 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 ` Multiple patch authors (was: Re: [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains) Borislav Petkov
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 [this message]
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=50894F8E.9060706@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=daniel@numascale-asia.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).