qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sunil Muthuswamy <sunilmut@microsoft.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: RE: [EXTERNAL] Re: qemu repo lockdown message for a WHPX PR
Date: Thu, 30 Jul 2020 21:53:47 +0000	[thread overview]
Message-ID: <SN4PR2101MB08802D6D26E0B811065DDF36C0710@SN4PR2101MB0880.namprd21.prod.outlook.com> (raw)
In-Reply-To: <c0ff07b6-87bb-f0da-d345-71e62e6c8ef6@gnu.org>

> 
> I was not referring to github pull requests, but rather to a maintainer
> pull request.  This is also sent to the mailing list.  There is no
> QEMU-specific documentation since maintainers are generally experienced
> enough to have observed how these are sent, but the Linux documentation
> more or less applies:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.kernel.org%2Fdoc%2Fhtml%2Flatest%2Fmaintainer%
> 2Fpull-
> requests.html&amp;data=02%7C01%7Csunilmut%40microsoft.com%7Cf67d260b255a455cfa1c08d833fdf333%7C72f988bf86f141
> af91ab2d7cd011db47%7C1%7C0%7C637316513089781442&amp;sdata=Kb4ZOLUxfq7kwrECGdyqKpeFX9SnIHSQcak64aVANYs%3
> D&amp;reserved=0
> 
> In any case, I suspect this misunderstanding is a sign that I should be
> handling WHPX patches for some more time, which I will gladly do. :)
> 
> Thanks!
> 
> Paolo
Thanks for the links. I think I understand it. The idea is to host a public WHPX qemu branch in my qemu github fork, host
all the signed-off WHPX patches there and every now and then, generate a 'pull-request' to merge those patches back to upstream.
Does that align with the expectation here?

      parent reply	other threads:[~2020-07-30 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 19:19 qemu repo lockdown message for a WHPX PR Sunil Muthuswamy
2020-07-29 20:05 ` Sunil Muthuswamy
2020-07-29 20:18   ` Eric Blake
2020-07-29 20:24     ` [EXTERNAL] " Sunil Muthuswamy
2020-07-29 20:28 ` Paolo Bonzini
2020-07-29 21:05   ` Peter Maydell
2020-07-30 21:53   ` Sunil Muthuswamy [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=SN4PR2101MB08802D6D26E0B811065DDF36C0710@SN4PR2101MB0880.namprd21.prod.outlook.com \
    --to=sunilmut@microsoft.com \
    --cc=bonzini@gnu.org \
    --cc=qemu-devel@nongnu.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).