From: Juan Quintela <quintela@redhat.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Mars 14th
Date: Mon, 14 Mar 2011 17:36:59 +0100 [thread overview]
Message-ID: <m3d3lthd5g.fsf@trasno.org> (raw)
In-Reply-To: <4D7E0AD4.10105@redhat.com> (Jes Sorensen's message of "Mon, 14 Mar 2011 13:32:20 +0100")
Jes Sorensen <Jes.Sorensen@redhat.com> wrote:
> On 03/14/11 13:14, Juan Quintela wrote:
>>
>> Please send any agenda items you are interested in covering.
>>
>> Thanks, Juan.
>
> I presume you mean for March 15? Today is the 14th and it is Monday :)
Dunno what calendar I looked to :p
Yes, you are right.
<#secure method=pgpmime mode=sign>
next prev parent reply other threads:[~2011-03-14 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 12:14 KVM call agenda for Mars 14th Juan Quintela
2011-03-14 12:32 ` [Qemu-devel] " Jes Sorensen
2011-03-14 16:36 ` Juan Quintela [this message]
2011-03-14 17:49 ` [Qemu-devel] " Anthony Liguori
2011-03-15 0:16 ` Yoshiaki Tamura
2011-03-15 13:50 ` Paolo Bonzini
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=m3d3lthd5g.fsf@trasno.org \
--to=quintela@redhat.com \
--cc=Jes.Sorensen@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