From: Eduardo Habkost <ehabkost@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Lukáš Doktor" <ldoktor@redhat.com>,
"Fam Zheng" <famz@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Amador Pahim" <apahim@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add Python scripts
Date: Fri, 15 Sep 2017 21:38:32 -0300 [thread overview]
Message-ID: <20170916003832.GF10621@localhost.localdomain> (raw)
In-Reply-To: <eabb65a2-cd0b-e968-2e19-c4c9ac3396a4@redhat.com>
On Fri, Sep 15, 2017 at 08:17:18PM -0400, John Snow wrote:
>
>
> On 09/15/2017 07:07 PM, Eduardo Habkost wrote:
> > Cleber and I are volunteering to review and queue patches for the
> > Python scripts and modules in scripts/.
> >
> > I'm setting "M: Odd fixes" because not all scripts are actively
> > maintained.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > Even before this patch is merged, I plan to send a pull request
> > including some patches for the Python code soon.
> > ---
> > MAINTAINERS | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 2c333aba21..2c3b8ecde7 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1390,6 +1390,13 @@ S: Maintained
> > F: include/sysemu/cryptodev*.h
> > F: backends/cryptodev*.c
> >
> > +Python scripts
> > +M: Eduardo Habkost <ehabkost@redhat.com>
> > +M: Cleber Rosa <crosa@redhat.com>
> > +S: Odd fixes
> > +F: scripts/qmp/*
> > +F: scripts/*.py
> > +
> > QAPI
> > M: Markus Armbruster <armbru@redhat.com>
> > M: Michael Roth <mdroth@linux.vnet.ibm.com>
> >
>
> I rather like the thought of having dedicated Python maintainers who can
> review python code with an eye for what is idiomatic. I am fairly
> certain the python I write is functional, but I'm rarely sure it's what
> a python programmer would do.
>
> I suppose you are intentionally omitting any python that exists as part
> of the test infrastructure, however?
Initially, yes. I was trying to include only the stuff we were
actively maintaining. But later I decided to use "S: Odd fixes"
instead of "S: Maintained", so I guess it won't hurt to include
this:
---
diff --git a/MAINTAINERS b/MAINTAINERS
index 2c3b8ecde7..876ac0df99 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1396,6 +1396,8 @@ M: Cleber Rosa <crosa@redhat.com>
S: Odd fixes
F: scripts/qmp/*
F: scripts/*.py
+F: tests/*.py
+K: #!.*python
QAPI
M: Markus Armbruster <armbru@redhat.com>
--
Eduardo
next prev parent reply other threads:[~2017-09-16 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 23:07 [Qemu-devel] [PATCH] MAINTAINERS: Add Python scripts Eduardo Habkost
2017-09-16 0:17 ` John Snow
2017-09-16 0:38 ` Eduardo Habkost [this message]
2017-09-18 9:40 ` Stefan Hajnoczi
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=20170916003832.GF10621@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=apahim@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@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=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).