From: John Snow <jsnow@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, crosa@redhat.com, alex.bennee@linaro.org
Subject: Re: [PATCH v2 1/1] MAINTAINERS: Add Python library stanza
Date: Wed, 23 Sep 2020 11:17:01 -0400 [thread overview]
Message-ID: <ce23c70a-2e0e-0ca1-5260-812d713f04a8@redhat.com> (raw)
In-Reply-To: <87wo0k34qp.fsf@dusky.pond.sub.org>
On 9/23/20 11:14 AM, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
>
>> I'm proposing that I split the actual Python library off from the other
>> miscellaneous python scripts we have and declare it maintained. Add
>> myself as a maintainer of this folder, along with Cleber.
>>
>> v2: change python/* to python/, thanks Alex.
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
>> Acked-by: Cleber Rosa <crosa@redhat.com>
>> Acked-by: Eduardo Habkost <ehabkost@redhat.com>
>> ---
>> MAINTAINERS | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 3d17cad19a..c0222ee645 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -2355,11 +2355,18 @@ S: Maintained
>> F: include/sysemu/cryptodev*.h
>> F: backends/cryptodev*.c
>>
>> +Python library
>> +M: John Snow <jsnow@redhat.com>
>> +M: Cleber Rosa <crosa@redhat.com>
>> +R: Eduardo Habkost <ehabkost@redhat.com>
>> +S: Maintained
>> +F: python/
>> +T: git https://gitlab.com/jsnow/qemu.git python
>> +
>> Python scripts
>> M: Eduardo Habkost <ehabkost@redhat.com>
>> M: Cleber Rosa <crosa@redhat.com>
>> S: Odd fixes
>> -F: python/qemu/*py
>> F: scripts/*.py
>> F: tests/*.py
>
> Separate sections just so you can have the appropriate S:, or is there a
> deeper logic behind the split?
>
Yes, different intended levels of support. I don't currently have the
bandwidth to promise support for the miscellaneous Python scripts in
./scripts, but I do promise to support to a higher level the code in
./python.
Over time, I intend to migrate things into ./python, but there are some
series that need to happen first before I start doing that.
--js
next prev parent reply other threads:[~2020-09-23 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 23:05 [PATCH v2 0/1] MAINTAINERS: Add Python library stanza John Snow
2020-09-22 23:05 ` [PATCH v2 1/1] " John Snow
2020-09-23 7:49 ` Philippe Mathieu-Daudé
2020-09-23 14:30 ` John Snow
2020-09-23 15:14 ` Markus Armbruster
2020-09-23 15:17 ` John Snow [this message]
2020-09-23 15:37 ` Eduardo Habkost
2020-09-23 16:49 ` Philippe Mathieu-Daudé
2020-09-24 6:58 ` Markus Armbruster
2020-10-01 15:27 ` John Snow
2020-10-01 15:49 ` Philippe Mathieu-Daudé
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=ce23c70a-2e0e-0ca1-5260-812d713f04a8@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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).