From: Gerd Hoffmann <kraxel@redhat.com>
To: Nathan Baum <nathan@parenthephobia.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] QemuOpts: command line switches for the config file.
Date: Fri, 16 Oct 2009 21:33:50 +0200 [thread overview]
Message-ID: <4AD8CA9E.50402@redhat.com> (raw)
In-Reply-To: <1255718902.25855.66.camel@localhost.localdomain>
On 10/16/09 20:48, Nathan Baum wrote:
> In the medium term, perhaps a "legacy_options" option which can be
> automatically parsed by -readconfig.
>
> In the short term, just put the non-QemuOpt options in a comment.
>
> (In the long term, hopefully there won't be any legacy options.)
Yes.
> I've knocked up something which does the short term solution.
Hmm, I'd prefer to simply ignore legacy options. Then join forces for
the long-term solution instead of implementing something temporary.
cheers,
Gerd
next prev parent reply other threads:[~2009-10-16 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 8:39 [Qemu-devel] [PATCH 0/4] QemuOpts: config file support Gerd Hoffmann
2009-10-14 8:39 ` [Qemu-devel] [PATCH 1/4] QemuOpts: add find_list() Gerd Hoffmann
2009-10-14 8:39 ` [Qemu-devel] [PATCH 2/4] QemuOpts: dump config Gerd Hoffmann
2009-10-14 18:56 ` Anthony Liguori
2009-10-14 8:39 ` [Qemu-devel] [PATCH 3/4] QemuOpts: parse config from file Gerd Hoffmann
2009-10-14 18:55 ` Anthony Liguori
2009-10-14 8:39 ` [Qemu-devel] [PATCH 4/4] QemuOpts: command line switches for the config file Gerd Hoffmann
2009-10-16 18:39 ` Nathan Baum
2009-10-16 19:29 ` Gerd Hoffmann
2009-10-16 18:48 ` Nathan Baum
2009-10-16 19:33 ` Gerd Hoffmann [this message]
2009-10-14 18:53 ` [Qemu-devel] [PATCH 0/4] QemuOpts: config file support Anthony Liguori
2009-10-14 19:01 ` Anthony Liguori
2009-10-16 10:16 ` Gerd Hoffmann
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=4AD8CA9E.50402@redhat.com \
--to=kraxel@redhat.com \
--cc=nathan@parenthephobia.org.uk \
--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).