[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 1/4] xen: sched: refector code around vcpu_deassign() in null scheduler

  • To: Dario Faggioli <dfaggioli@xxxxxxxx>
  • From: George Dunlap <George.Dunlap@xxxxxxxxxx>
  • Date: Tue, 6 Aug 2019 07:45:18 +0000
  • Accept-language: en-GB, en-US
  • Authentication-results: esa5.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=George.Dunlap@xxxxxxxxxx; spf=Pass smtp.mailfrom=George.Dunlap@xxxxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxx
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
  • Delivery-date: Tue, 06 Aug 2019 07:45:33 +0000
  • Ironport-sdr: xaHMzmK9s7F69NGGKi6HieNc6UWjdnaV0VRS2RgxMOvsgLq/24vR7W3rAh/hIRoQ39Ftz/gtOL 8Nz5OIVG7XFrWzGSTHFmZbPPwi+cpPeYvZzPeMNsO1aJ34qhy20SWohKGLhYuTneBT+/TEKkVb cJ0YOXKWLNA7zIvBebOQFALphd2FEKZIz75nZkelNxj9zRKqqqpT9WeL8qLD46HYrNEBgavWYm BzQyhB3aBsk4SbbwaPMTfmuWSgXKlG1wA6CsHJQ5wYf9jQeptoL/ql7eu1XVYf3updf1WnQVoe VNM=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHVQ3r7l7jEiRa2CU6PQPK00ehLoqbspLkAgAASh4CAAAcmAIAA7uUA
  • Thread-topic: [Xen-devel] [PATCH v2 1/4] xen: sched: refector code around vcpu_deassign() in null scheduler

> On Aug 5, 2019, at 6:30 PM, Dario Faggioli <dfaggioli@xxxxxxxx> wrote:
> On Mon, 2019-08-05 at 17:04 +0100, George Dunlap wrote:
>> On 8/5/19 4:58 PM, Jan Beulich wrote:
>>> On 26.07.2019 08:25, Dario Faggioli wrote:
>>> 1) The commit is empty, presumably because I did apply the patch a
>>> few
>>> days ago already.
>>> 2) The committer is recorded as "Patchew Importer <
>>> importer@xxxxxxxxxxx>".
>>> Do we really want to hide the fact who has been committing a patch?
>>> While it's mostly mechanical, there's still the human decision of
>>> "this
>>> is ready to go in" involved, which I don't think a bot can reliably
>>> take
>>> in all cases.
>> Both of these are mistakes, and due to the fact that I `git fetch`ed
>> patchew's commit rather than doing `git am` of the mbox provided by
>> patchew.  (And I used patchew's commit because somehow 4/4 didn't
>> reach
>> my inbox.)
> And this last part is apparently my fault, as your email address is
> actually wrong, in the Cc line of that patch.

That would explain it. :-)  But that’s by no means your “fault”: It’s very 
common for me to only be CC’d on a subset of patches in a series (e.g., because 
I’m the maintainer for some patches but not others), so “receiving a only a 
subset of patches” is something my workflow should handle effectively but 


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.