From: William Dauchy <william@gandi.net>
To: Markus Armbruster <armbru@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] readconfig with machine section and type option ignored
Date: Tue, 16 Dec 2014 13:38:31 +0100 [thread overview]
Message-ID: <20141216123831.GB5629@gandi.net> (raw)
In-Reply-To: <87tx0vbxuo.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
On Dec16 13:09, Markus Armbruster wrote:
> Broken since main()'s case QEMU_OPTION_machine doesn't just parse its
> option argument with qemu_opts_parse(), it also implements parameter
> "type". Copying Marcel because "he touched it, he owns it".
yes indeed, the type option is also not working, and there was an older
report about it
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-12-16 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 16:42 [Qemu-devel] readconfig with machine section and type option ignored William Dauchy
2014-12-16 12:09 ` Markus Armbruster
2014-12-16 12:38 ` William Dauchy [this message]
2014-12-16 13:41 ` Marcel Apfelbaum
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=20141216123831.GB5629@gandi.net \
--to=william@gandi.net \
--cc=armbru@redhat.com \
--cc=marcel@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).