From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] [PATCH v2] MAINTAINERS: Add an entry for qemu-options* files in main directory
Date: Thu, 4 Oct 2018 12:53:39 +0200 [thread overview]
Message-ID: <1538650419-7995-1-git-send-email-thuth@redhat.com> (raw)
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.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
v2: Create a separate entry
MAINTAINERS | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3275cc6..66c13f2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1522,6 +1522,14 @@ F: tests/test-qemu-opts.c
F: util/keyval.c
F: util/qemu-option.c
+Generic command line options
+M: Paolo Bonzini <pbonzini@redhat.com>
+R: Markus Armbruster <armbru@redhat.com>
+R: Thomas Huth <thuth@redhat.com>
+S: Maintained
+F: qemu-options*
+F: vl.c
+
Coverity model
M: Markus Armbruster <armbru@redhat.com>
S: Supported
--
1.8.3.1
next reply other threads:[~2018-10-04 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 10:53 Thomas Huth [this message]
2018-10-04 11:43 ` [Qemu-devel] [PATCH v2] MAINTAINERS: Add an entry for qemu-options* files in main directory Paolo Bonzini
2018-10-09 9:21 ` Markus Armbruster
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=1538650419-7995-1-git-send-email-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@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 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).