From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] qapi/misc.json is too big, let's bite off a few chunks
Date: Fri, 7 Jun 2019 10:33:14 +0200 [thread overview]
Message-ID: <47942a1d-efa4-c20d-a854-bd0e3b4ec1f2@redhat.com> (raw)
In-Reply-To: <875zphg9t8.fsf@dusky.pond.sub.org>
On 6/7/19 8:59 AM, Markus Armbruster wrote:
[...]
> QOM is not a particularly active subsystem now: 51 commits in two years.
>
> We obviously need maintainers to review and merge patches. The nominal
> maintainer hasn't been doing that since 2015. Git shows the following
> top committers taking on / getting sucked into QOM:
>
> Markus Armbruster <armbru@redhat.com>
> Eduardo Habkost <ehabkost@redhat.com>
> Paolo Bonzini <pbonzini@redhat.com>
> Marc-André Lureau <marcandre.lureau@redhat.com>
> Eric Blake <eblake@redhat.com>
>
> We really need nominal maintainer(s) again.
>
> Of course, *active* maintainers would be even better: I consider QOM
> stuck in an unhappy place where much of its potential is still
> potential.
>
> But let's start small. Volunteers for the reviewer role, please step
> forward :)
>
>
>
> The details I promised:
>
> Output of "scripts/get_maintainer.pl --git --git-since='2-years-ago' |
> grep commit_signer" sorted by file size:
>
[...]
> = include/qom/object_interfaces.h =
> Eduardo Habkost <ehabkost@redhat.com> (commit_signer:8/5=100%)
> Igor Mammedov <imammedo@redhat.com> (commit_signer:3/5=60%)
> "Marc-André Lureau" <marcandre.lureau@redhat.com> (commit_signer:2/5=40%)
> "Philippe Mathieu-Daudé" <f4bug@amsat.org> (commit_signer:2/5=40%)
> Eric Blake <eblake@redhat.com> (commit_signer:1/5=20%)
get_maintainer's commit_signer is lying...
[...]
> = qom/trace-events =
> Stefan Hajnoczi <stefanha@redhat.com> (commit_signer:2/2=100%)
> "Philippe Mathieu-Daudé" <philmd@redhat.com> (commit_signer:2/2=100%)
> Markus Armbruster <armbru@redhat.com> (commit_signer:1/2=50%)
> Michael Tokarev <mjt@tls.msk.ru> (commit_signer:1/2=50%)
This 'git log -p' history of this file is very interesting...
next prev parent reply other threads:[~2019-06-07 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 16:14 [Qemu-devel] qapi/misc.json is too big, let's bite off a few chunks Markus Armbruster
2019-05-24 18:31 ` Paolo Bonzini
2019-06-07 8:25 ` Markus Armbruster
2019-06-07 11:35 ` Paolo Bonzini
2019-06-07 12:45 ` Markus Armbruster
2019-06-11 21:20 ` Eduardo Habkost
2019-05-24 18:53 ` Eduardo Habkost
2019-05-27 8:00 ` Markus Armbruster
2019-05-27 10:03 ` Paolo Bonzini
2019-05-28 19:37 ` Eduardo Habkost
2019-06-07 6:59 ` Markus Armbruster
2019-06-07 8:33 ` Philippe Mathieu-Daudé [this message]
2019-06-07 12:25 ` Markus Armbruster
2019-06-07 9:59 ` Daniel P. Berrangé
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=47942a1d-efa4-c20d-a854-bd0e3b4ec1f2@redhat.com \
--to=philmd@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).