From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add an entry for qemu-options* files in main directory
Date: Tue, 12 Jun 2018 17:04:07 +0200 [thread overview]
Message-ID: <dcd08712-9dbd-eeda-7040-40b1afb14429@redhat.com> (raw)
In-Reply-To: <a16c729a-8856-1141-5a6f-e647624bab44@redhat.com>
On 12/06/2018 12:46, Thomas Huth wrote:
>>
>> Your patch does what is possible with a monolithic interface definition:
>> it dumps it all on one maintainer: me. I'm struggling to keep up with
>> the QAPI schema, I'm not sure I can take more.
>>
>> Note that "Command line option argument parsing" is phrased carefully:
>> it's not "CLI", not even "CLI parsing". qemu-options* does not fit
>> there. Two solutions: widen the section so it fits better, create a new
>> section. The latter would be closer to how we do QMP.
>>
>> What do you think?
> Both ideas sound fine to me. What about adding a new section called
> "Generic command line options"? I hope that the word "generic" then
> makes it clear that this entry is primarily thought for generic options
> - subsystem specific options can and should still go through the
> subsystem trees instead.
>
> Do you think you could still be available as (co-)maintainer of that new
> section? If not, who are going to be the maintainers of that new
> section? Paolo? Eric? Daniel? ...?
Well, currently it's going through me. I'd add vl.c too, by the way.
Paolo
next prev parent reply other threads:[~2018-06-12 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 5:20 [Qemu-devel] [PATCH] MAINTAINERS: Add an entry for qemu-options* files in main directory Thomas Huth
2018-06-11 15:53 ` Markus Armbruster
2018-06-12 10:46 ` Thomas Huth
2018-06-12 15:04 ` Paolo Bonzini [this message]
2018-06-13 6:23 ` Markus Armbruster
2018-06-13 12:37 ` Paolo Bonzini
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=dcd08712-9dbd-eeda-7040-40b1afb14429@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).