[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [EXTERNAL] Re: qemu repo lockdown message for a WHPX PR
|
From: |
Sunil Muthuswamy |
|
Subject: |
RE: [EXTERNAL] Re: qemu repo lockdown message for a WHPX PR |
|
Date: |
Thu, 30 Jul 2020 21:53:47 +0000 |
>
> 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&data=02%7C01%7Csunilmut%40microsoft.com%7Cf67d260b255a455cfa1c08d833fdf333%7C72f988bf86f141
> af91ab2d7cd011db47%7C1%7C0%7C637316513089781442&sdata=Kb4ZOLUxfq7kwrECGdyqKpeFX9SnIHSQcak64aVANYs%3
> D&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?