All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	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 12:46:26 +0200	[thread overview]
Message-ID: <a16c729a-8856-1141-5a6f-e647624bab44@redhat.com> (raw)
In-Reply-To: <87bmch48w6.fsf@dusky.pond.sub.org>

On 11.06.2018 17:53, Markus Armbruster wrote:
> Thomas Huth <thuth@redhat.com> writes:
> 
>> The file "qemu-options.h", "qemu-options.hx" and "qemu-options-wrapper.h"
>> in the main directory are currently without maintainer according to our
>> get_maintainers.pl script. Considering that the command line options are
>> a public interface and thus quite important, this is quite a bad state.
>> So I'd like to suggest to add these files to the "Command line option
>> argument parsing" section now.
>>
>> And since I'm interested in the command line interface of QEMU, add
>> myself as reviewer here.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>  MAINTAINERS | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e187b1f..6aa19dc 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1413,7 +1413,9 @@ F: chardev/baum.c
>>  
>>  Command line option argument parsing
>>  M: Markus Armbruster <armbru@redhat.com>
>> +R: Thomas Huth <thuth@redhat.com>
>>  S: Supported
>> +F: qemu-options*
>>  F: include/qemu/option.h
>>  F: tests/test-keyval.c
>>  F: tests/test-qemu-opts.c
> 
> CLI is like QMP in that there's infrastructure, interface and
> implementation.
> 
> QMP infrastructure is MAINTAINERS sections QMP and QAPI.  These are
> proper subsystems, with clear boundaries.  Its maintainers get copied on
> relatively few patches.
> 
> QMP infrastructure doesn't own the actual commands[1], subsystems do.
> For instance, the block subsystem owns commands dealing with block
> devices.
> 
> The QMP interface is specified in the QAPI schema.  Again, QMP
> infrastructure doesn't own it, subsystems do.  However, to maintain some
> measure of cohesion, we co-maintain the interface: MAINTAINERS section
> QAPI schema covers the complete schema, and subsystems cover individual
> modules of the schema[2].
> 
> I think a similar arrangement make sense for CLI.  We'll get it for free
> with CLI QAPIfication, but that'll take time.
> 
> 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? ...?

 Thomas

  reply	other threads:[~2018-06-12 10:46 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 [this message]
2018-06-12 15:04     ` Paolo Bonzini
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=a16c729a-8856-1141-5a6f-e647624bab44@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.