From: Anthony Liguori <anthony@codemonkey.ws>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] -readconfig: accept fd=<fd> option (v2)
Date: Mon, 19 Mar 2012 11:55:10 -0500 [thread overview]
Message-ID: <4F6764EE.8010108@codemonkey.ws> (raw)
In-Reply-To: <20120319165128.GM9375@otherpad.lan.raisama.net>
On 03/19/2012 11:51 AM, Eduardo Habkost wrote:
> On Mon, Mar 19, 2012 at 11:45:00AM -0500, Anthony Liguori wrote:
>>> On the other hand, I:
>>>
>>> - Would like to let the user (a human) list where are the default config
>>> files being used by Qemu;
>>
>> This should be provided via a QMP command and as part of
>> -query-capabilities (see previous series).
>
> Is this usable by a human?
It surely is for the users that would care about this.
Normally, this stuff is printed in either --help or --version FWIW. But we
can't touch either because of libvirt (hence my other series). So if we fix
that problem, we can provide a nicer --help/--version output that has this
information.
Regards,
Anthony Liguori
>
prev parent reply other threads:[~2012-03-19 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 14:54 [Qemu-devel] [PATCH 0/3] -readconfig: accept fd=<fd> option (v2) Eduardo Habkost
2012-03-19 14:54 ` [Qemu-devel] [PATCH 1/3] qemu-config.h: include qemu-option.h Eduardo Habkost
2012-03-19 14:54 ` [Qemu-devel] [PATCH 2/3] -readconfig: use QemuOpts option format (v2) Eduardo Habkost
2012-03-19 14:54 ` [Qemu-devel] [PATCH 3/3] -readconfig: accept fd=<fd> option (v2) Eduardo Habkost
2012-03-19 15:10 ` [Qemu-devel] [PATCH 0/3] " Anthony Liguori
2012-03-19 15:37 ` Eduardo Habkost
2012-03-19 15:39 ` Anthony Liguori
2012-03-19 16:06 ` Eduardo Habkost
2012-03-19 16:21 ` Anthony Liguori
2012-03-19 16:39 ` Eduardo Habkost
2012-03-19 16:45 ` Anthony Liguori
2012-03-19 16:51 ` Eduardo Habkost
2012-03-19 16:55 ` Anthony Liguori [this message]
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=4F6764EE.8010108@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=ehabkost@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).