On Mon, Jul 01, 2019 at 07:17:39PM -0400, John Snow wrote:
>
>
> On 7/1/19 5:27 PM, Eduardo Habkost wrote:
> > On Thu, Jun 27, 2019 at 05:32:17PM -0400, John Snow wrote:
> >> I didn't actually mean to retain the RFC tag, but oh well.
> >
> > I'm queueing patch 1-2 for QEMU 4.1.
> >
> > Patch 3
On 7/1/19 5:27 PM, Eduardo Habkost wrote:
> On Thu, Jun 27, 2019 at 05:32:17PM -0400, John Snow wrote:
>> I didn't actually mean to retain the RFC tag, but oh well.
>
> I'm queueing patch 1-2 for QEMU 4.1.
>
> Patch 3 will require more careful review. If you can demonstrate
> it fixes a probl
On Thu, Jun 27, 2019 at 05:32:17PM -0400, John Snow wrote:
> I didn't actually mean to retain the RFC tag, but oh well.
I'm queueing patch 1-2 for QEMU 4.1.
Patch 3 will require more careful review. If you can demonstrate
it fixes a problem in some use cases, we can call it a bug fix
and include
I didn't actually mean to retain the RFC tag, but oh well.
On 6/27/19 5:28 PM, John Snow wrote:
> There's a lot of code hiding in what is ostensibly a package
> configuration file. Let's break that out into something more visible.
>
> V2:
> - Retain python 2.7+ compatibility :(
> - Refactor shu
There's a lot of code hiding in what is ostensibly a package
configuration file. Let's break that out into something more visible.
V2:
- Retain python 2.7+ compatibility :(
- Refactor shutdown a little more aggressively
John Snow (3):
python/qemu: split QEMUMachine out from underneath __init_
