From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
Date: Fri, 12 Mar 2010 10:42:42 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1003121024590.27222@kaball-desktop> (raw)
In-Reply-To: <201003121123.33935.sheng@linux.intel.com>
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.
> Another thing is, you were keeping using my old patches as your base, while I
> was working with the reviewers to update the patch quickly. I don't think
> that's a kind of respect to both reviewers' and my work. You would duplicate
> reviewer's effect, especially you always repost the whole patch(and drop my
> authorship) rather than the different part. I've split patches in order to
> provide a code base for further development, but you complete ignored them and
> keeping post the whole patchset based on my old patches.
>
I don't keep using your old patches as a base but I manually rebase over
the most recent patch series you sent every time.
Obviously it is not a perfect system and sometimes I can miss something,
this is why at the beginning I asked you to work together on the same
tree: I wanted to avoid exactly this sort of issues.
My intentions are true so my proposal of working on a common tree is
still valid, just let me know when you are interested.
next prev parent reply other threads:[~2010-03-12 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 15:46 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 10:42 ` Stefano Stabellini [this message]
2010-03-12 21:53 ` Jeremy Fitzhardinge
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=alpine.DEB.2.00.1003121024590.27222@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sheng@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®