From: Eric Blake <eblake@redhat.com>
To: quintela@redhat.com
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenda for 2013-04-23
Date: Mon, 22 Apr 2013 10:31:15 -0600 [thread overview]
Message-ID: <517565D3.2040304@redhat.com> (raw)
In-Reply-To: <87wqruwnne.fsf@elfo.elfo>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
On 04/22/2013 10:11 AM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda topics you are interested in.
* What can libvirt expect in 1.5 for introspection of command-line support?
* What are the rules for adding optional parameters to existing QMP
commands? Would it help if we had introspection of QMP commands?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
prev parent reply other threads:[~2013-04-22 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 16:11 KVM call agenda for 2013-04-23 Juan Quintela
2013-04-22 16:16 ` Paolo Bonzini
2013-04-22 16:31 ` Eric Blake [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=517565D3.2040304@redhat.com \
--to=eblake@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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