From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: quintela@redhat.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org,
KVM devel mailing list <kvm@vger.kernel.org>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] KVM call agenda for May 10th
Date: Tue, 10 May 2011 15:20:53 +0200 [thread overview]
Message-ID: <4DC93BB5.1060403@redhat.com> (raw)
In-Reply-To: <m3tyd4hz3i.fsf@neno.mitica>
On 05/09/11 13:50, Juan Quintela wrote:
>
> Please send in any agenda items you are interested in covering.
>
> From last week, we have already:
>
> - import kvm headers into qemu, drop #ifdef maze (Jan)
>
> Thanks, Juan.
>
Since we haven't received any further agenda items. In addition Anthony
is unavailable, plus all the guys in Tel Aviv is on holiday today - lets
postpone until next week.
CANCELED!
Jes
prev parent reply other threads:[~2011-05-10 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 11:50 [Qemu-devel] KVM call agenda for May 10th Juan Quintela
2011-05-10 13:20 ` Jes Sorensen [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=4DC93BB5.1060403@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.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;
as well as URLs for NNTP newsgroup(s).