From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Sheng Yang <sheng@linux.intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
Date: Fri, 12 Mar 2010 13:53:18 -0800 [thread overview]
Message-ID: <4B9AB7CE.5090601@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003121024590.27222@kaball-desktop>
On 03/12/2010 02:42 AM, Stefano Stabellini wrote:
> On Fri, 12 Mar 2010, Sheng Yang wrote:
>
>> On Wednesday 10 March 2010 23:46:54 Stefano Stabellini wrote:
>>
>>> Hi all,
>>>
>> Stefano,
>>
>> And next time when you send out the patch, please be more respect to my work.
>>
>> You dropped all the original author(me) of patchset, and only add a sign-off
>> for me. If you don't aware the difference, here is a snippet of
>> linux/Documentation/SummittingPatches
>>
>>
> I am truly sorry and apologise for it, I would never want to give you
> the impression of being disrespectful of you and your work.
> If you pay attention I manually wrote in the comments of all the past
> versions of the patches that you were the original author, this time I
> just forgot.
> I guess it is really the time I start using git-send-email :)
>
> Your work has been really important for my series and you deserve the
> credit for it independently from which patch series gets applied.
>
Best practise for this kind of thing is to use Sheng's patch verbatim,
then apply a separate delta on top to make the changes you want. That way:
* credit can be property attributed
* it helps with maintaining two parallel-but-converging git
branches, because all the common stuff is genuinely common, and
the variations can work from there, and
* if Sheng updates his patches (review, bugfix, etc), then we can
easily see how those changes affect your changes.
For example, I just rebased your previous patch posting so that it is
rooted on Sheng's two base patches, as they're completely common.
The latest of both patches is in xen/pvhvm-sheng and -stefano.
J
prev parent reply other threads:[~2010-03-12 21:53 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 15:46 [PATCH 0 of 5] PV on HVM Xen Stefano Stabellini
2010-03-10 17:33 ` [Xen-devel] " Pasi Kärkkäinen
2010-03-10 17:55 ` Stefano Stabellini
2010-03-10 19:45 ` Jeremy Fitzhardinge
2010-03-12 3:23 ` Sheng Yang
2010-03-12 3:23 ` Sheng Yang
2010-03-12 10:42 ` [Xen-devel] " Stefano Stabellini
2010-03-12 16:00 ` Stefano Stabellini
2010-03-15 4:05 ` Sheng Yang
2010-03-15 8:29 ` Sheng Yang
2010-03-15 12:22 ` Stefano Stabellini
2010-03-17 9:38 ` Sheng Yang
2010-03-17 14:18 ` Konrad Rzeszutek Wilk
2010-03-17 15:21 ` Stefano Stabellini
2010-03-17 16:13 ` Jeremy Fitzhardinge
2010-03-18 1:30 ` Sheng Yang
2010-03-19 20:38 ` Jeremy Fitzhardinge
2010-03-22 6:26 ` MSI proposal and work transfer...(was: Re: [PATCH 0 of 5] PV on HVM Xen) Sheng Yang
2010-03-23 20:47 ` Jeremy Fitzhardinge
2010-03-24 8:19 ` Sheng Yang
2010-03-23 23:16 ` Stefano Stabellini
2010-03-24 8:25 ` Sheng Yang
2010-03-18 2:19 ` [PATCH 0 of 5] PV on HVM Xen Sheng Yang
2010-03-18 16:42 ` Jeremy Fitzhardinge
2010-03-17 16:13 ` Jeremy Fitzhardinge
2010-03-15 12:28 ` Stefano Stabellini
2010-03-15 23:08 ` Jeremy Fitzhardinge
2010-03-15 23:24 ` Frank van der Linden
2010-03-16 0:32 ` Dan Magenheimer
2010-03-16 6:09 ` Sheng Yang
2010-03-16 16:46 ` Dan Magenheimer
2010-03-16 11:07 ` Stefano Stabellini
2010-03-16 17:23 ` Jeremy Fitzhardinge
2010-03-16 17:32 ` Stefano Stabellini
2010-03-16 17:41 ` Jeremy Fitzhardinge
2010-03-16 18:06 ` Stefano Stabellini
2010-03-16 18:26 ` Jeremy Fitzhardinge
2010-03-16 18:37 ` Stefano Stabellini
2010-03-17 8:51 ` Sheng Yang
2010-03-17 9:18 ` Sheng Yang
2010-03-17 15:17 ` Stefano Stabellini
2010-03-17 18:20 ` Ian Campbell
2010-03-18 1:42 ` Sheng Yang
2010-03-18 1:35 ` Sheng Yang
2010-03-18 14:22 ` Stefano Stabellini
2010-03-18 16:50 ` Jeremy Fitzhardinge
2010-03-18 17:30 ` Jeremy Fitzhardinge
2010-03-12 21:53 ` Jeremy Fitzhardinge [this message]
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=4B9AB7CE.5090601@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.