From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH][STABLE] Don't set default monitor when there is a mux'ed one
Date: Thu, 14 Jan 2010 09:07:47 -0600 [thread overview]
Message-ID: <4B4F3343.1030809@codemonkey.ws> (raw)
In-Reply-To: <4B4F2F06.2040301@siemens.com>
On 01/14/2010 08:49 AM, Jan Kiszka wrote:
> This fixes eg. "-nographic -serial mon:stdio [-serial ...]".
>
Is this really an appropriate invocation though?
-nographic != mon:stdio so the semantics of how this is supposed to
behave is at best ill-defined.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-14 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 14:49 [Qemu-devel] [PATCH][STABLE] Don't set default monitor when there is a mux'ed one Jan Kiszka
2010-01-14 14:58 ` [Qemu-devel] " Gerd Hoffmann
2010-01-14 15:07 ` Anthony Liguori [this message]
2010-01-14 15:19 ` [Qemu-devel] " Jan Kiszka
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=4B4F3343.1030809@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@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).