From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for November 29
Date: Mon, 28 Nov 2011 16:30:30 +0200 [thread overview]
Message-ID: <4ED39B06.10002@redhat.com> (raw)
In-Reply-To: <4ED39A82.5060501@codemonkey.ws>
On 11/28/2011 04:28 PM, Anthony Liguori wrote:
> On 11/28/2011 08:24 AM, Juan Quintela wrote:
>>
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> - 1.1 development window logistics
(somewhat related) memory API conversion queue merge plan
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-28 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 14:24 [Qemu-devel] KVM call agenda for November 29 Juan Quintela
2011-11-28 14:28 ` Anthony Liguori
2011-11-28 14:30 ` Avi Kivity [this message]
2011-11-28 14:35 ` Anthony Liguori
2011-11-28 15:34 ` Avi Kivity
2011-11-29 13:25 ` Juan Quintela
2011-11-29 13:57 ` Anthony Liguori
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=4ED39B06.10002@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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;
as well as URLs for NNTP newsgroup(s).