From: Paolo Bonzini <pbonzini@redhat.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 24
Date: Tue, 24 Jan 2012 15:03:33 +0100 [thread overview]
Message-ID: <4F1EBA35.20902@redhat.com> (raw)
In-Reply-To: <4F1EB8AF.3080804@codemonkey.ws>
On 01/24/2012 02:57 PM, Anthony Liguori wrote:
>> Please send in any agenda items you are interested in covering.
>
> I don't have anything pressing. I vote to cancel the call.
Nothing that cannot be discussed by email, but anyway here are a couple
of topics:
* qtest/libos: Python or C?
* QOM merge: what about a "new device freeze" for 1.1 around mid February?
Paolo
next prev parent reply other threads:[~2012-01-24 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 17:38 [Qemu-devel] KVM call agenda for Tuesday 24 Markus Armbruster
2012-01-24 13:57 ` Anthony Liguori
2012-01-24 14:03 ` Paolo Bonzini [this message]
2012-01-24 14:08 ` Anthony Liguori
2012-01-24 14:30 ` Kevin Wolf
2012-01-24 14:53 ` Paolo Bonzini
2012-01-24 14:32 ` Markus Armbruster
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=4F1EBA35.20902@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=kvm@vger.kernel.org \
--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).