From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Ronnie Sahlberg <ronniesahlberg@gmail.com>
Subject: [Qemu-devel] [RFC PATCH 0/2] -readconfig: accept fd=<fd> option
Date: Tue, 13 Mar 2012 17:53:23 -0300 [thread overview]
Message-ID: <1331672005-30798-1-git-send-email-ehabkost@redhat.com> (raw)
This changes -readconfig to use the QemuOpts syntax and accept 'fd=<fd>' as
argument, too.
I'm not sure yet if it's OK to break compatibility of -readconfig for filenames
containing "=" or ",". On the one hand I wouldn't like to break it, on the
other hand, I wouldn't like to add Yet Another command-line option and make
-readconfig a legacy option.
Eduardo Habkost (2):
-readconfig: use QemuOpts option format
-readconfig: accept fd=<fd> option
qemu-config.c | 99 +++++++++++++++++++++++++++++++++++++++++++++++++++---
qemu-config.h | 8 ++++-
qemu-options.hx | 6 ++--
vl.c | 6 ++--
4 files changed, 106 insertions(+), 13 deletions(-)
--
1.7.3.2
next reply other threads:[~2012-03-13 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 20:53 Eduardo Habkost [this message]
2012-03-13 20:53 ` [Qemu-devel] [RFC PATCH 1/2] -readconfig: use QemuOpts option format Eduardo Habkost
2012-03-13 20:53 ` [Qemu-devel] [RFC PATCH 2/2] -readconfig: accept fd=<fd> option Eduardo Habkost
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=1331672005-30798-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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).