From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: KVM call agenda for 2013-05-21
Date: Tue, 21 May 2013 16:00:50 +0200 [thread overview]
Message-ID: <87txlwl9f1.fsf@elfo.elfo> (raw)
In-Reply-To: <87fvxhnck4.fsf@elfo.elfo> (Juan Quintela's message of "Mon, 20 May 2013 12:57:47 +0200")
Juan Quintela <quintela@redhat.com> wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
As our fearless leader is missing, we cancell the call.
(mst agreed on irc)
See you next week.
Later, Juan.
prev parent reply other threads:[~2013-05-21 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 10:57 KVM call agenda for 2013-05-21 Juan Quintela
2013-05-20 13:25 ` Michael S. Tsirkin
2013-05-21 12:18 ` Anthony Liguori
2013-05-21 12:33 ` Michael S. Tsirkin
2013-05-21 14:29 ` Anthony Liguori
2013-05-21 14:34 ` Juan Quintela
2013-05-21 16:40 ` [Qemu-devel] " Andreas Färber
2013-05-21 17:52 ` Michael S. Tsirkin
2013-05-21 17:53 ` Michael S. Tsirkin
2013-05-21 18:59 ` Anthony Liguori
2013-05-21 14:00 ` Juan Quintela [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=87txlwl9f1.fsf@elfo.elfo \
--to=quintela@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