From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
QEMU Developer <qemu-devel@nongnu.org>
Subject: [Qemu-devel] KVM call for agenda for 2016-03-01
Date: Tue, 23 Feb 2016 16:33:54 +0100 [thread overview]
Message-ID: <87mvqr7865.fsf@emacs.mitica> (raw)
Hi
Please, send any topic that you are interested in covering.
At the end of Monday I will send an email with the agenda or the
cancellation of the call, so hurry up.
After discussions on the QEMU Summit, we are going to have always open a
KVM call where you can add topics.
Call details:
By popular demand, a google calendar public entry with it
https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
(Let me know if you have any problems with the calendar entry. I just
gave up about getting right at the same time CEST, CET, EDT and DST).
If you need phone number details, contact me privately
Thanks, Juan.
next reply other threads:[~2016-02-23 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 15:33 Juan Quintela [this message]
2016-02-25 8:40 ` [Qemu-devel] KVM call for agenda for 2016-03-01 Thomas Huth
2016-02-25 12:47 ` Peter Krempa
2016-02-25 17:19 ` Eduardo Habkost
2016-03-01 13:56 ` Christian Borntraeger
2016-03-01 13:49 ` 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=87mvqr7865.fsf@emacs.mitica \
--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;
as well as URLs for NNTP newsgroup(s).