qemu-block
[Top][All Lists]
Advanced

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

Re: [PATCH RFC 00/32] python/qemu: refactor as installable package


From: John Snow
Subject: Re: [PATCH RFC 00/32] python/qemu: refactor as installable package
Date: Mon, 18 May 2020 10:15:29 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0


On 5/18/20 8:41 AM, Philippe Mathieu-Daudé wrote:
> On 5/14/20 7:53 AM, John Snow wrote:
> 
>>    python//qmp.py: use True/False for non/blocking modes
>>    python//qmp.py: Define common types
>>    python//qmp.py: re-absorb MonitorResponseError
>>    python//qmp.py: Do not return None from cmd_obj
>>    python//qmp.py: add casts to JSON deserialization
>>    python//qmp.py: add QMPProtocolError
>>    python//qmp.py: assert sockfile is not None
>>    python//machine.py: remove logging configuration
>>    python//machine.py: Fix monitor address typing
>>    python//machine.py: reorder __init__
>>    python//machine.py: Don't modify state in _base_args()
>>    python//machine.py: Handle None events in event_wait
>>    python//machine.py: use qmp.command
>>    python//machine.py: Add _qmp access shim
>>    python//machine.py: fix _popen access
>>    python//qtest.py: Check before accessing _qtest
> 
> Maybe remove double // in patch subjects :)
> 

Sure, if it's causing problems. I meant to imply an elided path
structure. I guess I can do e.g.

"python/qmp"
"python/machine"

and so on, if it matters. We don't really have a standard or anything.
Let me know what you'd prefer and I'll happily change it.

¯\_(ツ)_/¯




reply via email to

[Prev in Thread] Current Thread [Next in Thread]