qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2] MAINTAINERS: Add an entry for qemu-options*


From: Markus Armbruster
Subject: Re: [Qemu-devel] [PATCH v2] MAINTAINERS: Add an entry for qemu-options* files in main directory
Date: Tue, 09 Oct 2018 11:21:32 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Paolo Bonzini <address@hidden> writes:

> On 04/10/2018 12:53, Thomas Huth wrote:
>> 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.
>> Add an entry for these files which is maintained by Paolo, since the
>> option handling is tightly coupled with the code in vl.c (that Paolo
>> already handles via the "Main loop" entry).
>> 
>> And since I'm interested in the command line interface of QEMU, add
>> myself (and also Markus) as reviewer here.
>
> Sometimes, a file is really only touched as part of changes to other
> files.  Command line options can be changed by block device patches,
> vl.c patches, or something else.  I think changes to qemu-options* alone

Yes.  But when the file in question is an important interface, having
someone in charge of interface design aspects makes sense all the same.
Without that, consistency is left to chance.

Of course, you might say that command line consistency is FUBAR anyway.
You'd have a point.

> are quite rare, and I'd rather not have more stuff added to my misc tree
> (and my inbox)...

Same here.

I serve in such a role for the QAPI schema, together with Eric.  I feel
like I'm pretty consistently failing at keeping up (pardon the pun).  I
haven't thrown in the towel only because I also feel the guidance I
manage to provide there is better than nothing.  But I'd rather not take
on more.

Note that once my project to QAPIfy the CLI (on hold due to other
obligations) is complete, the CLI will be specified in the QAPI schema,
effectively dumping it on the QAPI schema maintainers.  I guess I'm a
sucker for punishment.  Just not right now, please.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]