From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for Jan 4
Date: Tue, 04 Jan 2011 08:33:25 -0600 [thread overview]
Message-ID: <4D232FB5.2090900@linux.vnet.ibm.com> (raw)
In-Reply-To: <4D232F56.8090001@redhat.com>
On 01/04/2011 08:31 AM, Jes Sorensen wrote:
> On 01/03/11 11:57, Juan Quintela wrote:
>
>> Please send any agenda items you are interested in covering.
>>
>> thanks, Juan.
>>
>>
> Do we have anything for the agenda yet?
>
I could use the extra hour to catch up from the Holiday (as I assume a
lot of folks could). I'd suggest cancelling.
And happy new year to everyone! :-)
Regards,
Anthony Liguori
> Jes
>
next prev parent reply other threads:[~2011-01-04 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 10:57 [Qemu-devel] KVM call agenda for Jan 4 Juan Quintela
2011-01-04 14:31 ` Jes Sorensen
2011-01-04 14:33 ` Anthony Liguori [this message]
2011-01-04 14:43 ` Jes Sorensen
2011-01-04 14:34 ` [Qemu-devel] " Juan Quintela
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=4D232FB5.2090900@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=Jes.Sorensen@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;
as well as URLs for NNTP newsgroup(s).