From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call minutes for July 6
Date: Tue, 06 Jul 2010 16:46:00 +0200 [thread overview]
Message-ID: <m3sk3wpt1z.fsf@trasno.mitica> (raw)
Today was a short call as Anthony didn't attend.
- Jes reminded people that Linux Plumbers deadline is July 19th
- Qemu 0.13 (from the agenda, we didn't discuss it without Anthony).
List of patches missing commit/comment/review from Anthony. We decided
to send to the list an initial list, and anybody that has anything empty
just anwer to this email. Juan (i.e. me) was "voluntered" to keep that
list. In this list there is:
- migration subsections (juan) will resend today
- migration ide: we are in a mess, will resend with subsections.
- migration memory with names. Allows migration with hotplug/hotunplug
(Alex), it is waiting for comments.
- <put your patches here>
Later, Juan.
next reply other threads:[~2010-07-06 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 14:46 Juan Quintela [this message]
2010-07-06 15:29 ` [Qemu-devel] KVM call minutes for July 6 Cam Macdonell
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=m3sk3wpt1z.fsf@trasno.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