From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, John Snow <jsnow@redhat.com>
Cc: "Lukáš Doktor" <ldoktor@redhat.com>,
qemu-devel@nongnu.org, famz@redhat.com, ehabkost@redhat.com,
apahim@redhat.com, f4bug@amsat.org, mreitz@redhat.com,
"Daniel P. Berrange" <berrange@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 00/10] qemu.py: Pylint/style fixes
Date: Tue, 22 Aug 2017 15:56:42 +0200 [thread overview]
Message-ID: <dc249ce1-5707-ddaf-8df7-fe960e86038f@redhat.com> (raw)
In-Reply-To: <87bmn8qd3z.fsf@dusky.pond.sub.org>
On 22/08/2017 09:24, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
>
>> On 08/18/2017 10:26 AM, Lukáš Doktor wrote:
>>> Hello guys,
>>>
>>> I'm reading the available python modules to exercise qemu and while reading them
>>> I fixed some issues that caught my attention. It usually starts with a simple
>>> pylint/docstring fixes and slowly graduates to more controversial ones so I'm
>>> open to suggestion to remove some of them.
>>>
>>> Kind regards,
>>> Lukáš
>>>
>>> Changes in v2
>>> - Squashed 2nd and 10th patches into 2nd one
>>> - Use repr() in MonitorResponseError's description
>>> - Improved commit message of the 6th patch
>>> - Two tweaks to docstrings changed in the 6th patch
>>> - Also updated qmp-shell to use new-style super calls (7th patch)
>>> - Fixed the accidental rename of qmp `cmd_id` (kept the id->cmd_id patch)
>>> - Changed the style of the style-fix in the 10th commit
>>>
>>> Changes in v3
>>> - Don't use repr in the 5th patch in MonitorResponseError
>>>
>>> Changes in v4
>>> - Use correct git base (remove unwanted commits)
>>>
>>> Changes in v5
>>> - Avoid bool comparison
>>> - Change report to return in one docstring
>>> - Removed the unnecessary spaces around single-line docstring
>>>
>>> Changes in v6
>>> - Bunch of docstring tweaks by Markus Armbruster
>>> - Line break in <80 chars
>>> - result dict => response dict
>>> - Removed the "event_match" rename
>>>
>>
>> Looks like all ten patches have an R-B despite changes; but it looks
>> like nothing particularly major was changed anyway.
>>
>> Does this fall under Markus's jurisdiction?
>>
>> (Well, except for qtest.py which seemingly has double-extra-no
>> maintainer...!)
>
> qemu.py is about starting and controlling QEMU, commonly for testing
> purposes. It's related to QMP only by virtue of using QMP for control
> (well, what else could it use?); if that makes me maintainer, I'll soon
> maintain basically all tests :)
>
> As far as I can tell, qemu.py's main user is still qemu-iotests, via
> qtest.py. Dan factored it out to make it available for
> tests/migration/guestperf/.
>
> Options for maintaining qemu.py and qtest.py:
>
> * Maintain them with qemu-iotest
>
> Currently mainained with the block layer core, by Kevin and Max.
>
> - Keep it that way
>
> - Appoint qemu-iotest maintainer(s).
>
> * Maintain them separately, say as "Python qtest support", appoint
> maintainer(s)
>
> Dan appears to be a hot contender:
>
> $ scripts/get_maintainer.pl -f --git-blame scripts/qtest.py
> Fam Zheng <famz@redhat.com> (authored lines:71/110=65%,commits:1/3=33%)
> "Daniel P. Berrange" <berrange@redhat.com> (authored lines:39/110=35%,commits:2/3=67%)
> Max Reitz <mreitz@redhat.com> (commits:2/3=67%)
> Amit Shah <amit.shah@redhat.com> (commits:1/3=33%)
> Stefan Hajnoczi <stefanha@redhat.com> (commits:1/3=33%)
> qemu-devel@nongnu.org (open list:All patches CC here)
> $ scripts/get_maintainer.pl -f --git-blame scripts/qemu.py
> "Daniel P. Berrange" <berrange@redhat.com> (authored lines:217/229=95%,commits:2/4=50%)
> Eduardo Habkost <ehabkost@redhat.com> (authored lines:12/229=5%,commits:4/4=100%)
> Markus Armbruster <armbru@redhat.com> (commits:1/4=25%)
> Max Reitz <mreitz@redhat.com> (commits:1/4=25%)
> Amit Shah <amit.shah@redhat.com> (commits:1/4=25%)
> qemu-devel@nongnu.org (open list:All patches CC here)
>
> Eduardo made the mistake^W^W^Wgraciously volunteered to maintain
> scripts/qmp/qmp-shell, which is also used for testing. Perhaps he'd
> be willing to maintain these guys as well.
>
> * Do nothing
>
> Hope "somebody" will take pity and merge patches. A common value of
> "somebody" would be Paolo.
Paolo is disappearing for two weeks starting Saturday, so you have
plenty of time to find another solution. :)
Paolo
next prev parent reply other threads:[~2017-08-22 13:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 14:26 [Qemu-devel] [PATCH v6 00/10] qemu.py: Pylint/style fixes Lukáš Doktor
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 01/10] " Lukáš Doktor
2017-08-24 22:38 ` Cleber Rosa
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 02/10] qemu|qtest: Avoid dangerous arguments Lukáš Doktor
2017-08-24 22:55 ` Cleber Rosa
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 03/10] qemu.py: Use iteritems rather than keys() Lukáš Doktor
2017-08-24 22:56 ` Cleber Rosa
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 04/10] qemu.py: Simplify QMP key-conversion Lukáš Doktor
2017-08-24 22:59 ` Cleber Rosa
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 05/10] qemu.py: Use custom exceptions rather than Exception Lukáš Doktor
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 06/10] qmp.py: Couple of pylint/style fixes Lukáš Doktor
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 07/10] qmp.py: Use object-based class for QEMUMonitorProtocol Lukáš Doktor
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 08/10] qmp.py: Avoid "has_key" usage Lukáš Doktor
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 09/10] qmp.py: Avoid overriding a builtin object Lukáš Doktor
2017-08-18 14:26 ` [Qemu-devel] [PATCH v6 10/10] qtest.py: Few pylint/style fixes Lukáš Doktor
2017-08-21 21:51 ` [Qemu-devel] [PATCH v6 00/10] qemu.py: Pylint/style fixes John Snow
2017-08-22 7:24 ` Markus Armbruster
2017-08-22 10:19 ` Philippe Mathieu-Daudé
2017-08-22 19:07 ` Eduardo Habkost
2017-08-24 12:15 ` Stefan Hajnoczi
2017-08-24 12:49 ` Philippe Mathieu-Daudé
2017-08-22 13:56 ` Paolo Bonzini [this message]
2017-08-22 18:11 ` John Snow
2017-08-22 18:51 ` Eduardo Habkost
2017-08-30 21:18 ` Eduardo Habkost
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=dc249ce1-5707-ddaf-8df7-fe960e86038f@redhat.com \
--to=pbonzini@redhat.com \
--cc=apahim@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=ldoktor@redhat.com \
--cc=mreitz@redhat.com \
--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).