From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for November 15th
Date: Tue, 15 Nov 2011 10:06:24 -0600 [thread overview]
Message-ID: <4EC28E00.3050205@codemonkey.ws> (raw)
In-Reply-To: <m3ty66wqcn.fsf@trasno.mitica>
On 11/14/2011 11:44 AM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
>
> Proposal:
> - Migration debacle.
Just to capture my action items so I don't forget:
1) write up a markdown document for qemu.git that describes the past, current,
and future state of storage requirements for migration
2) write up the notes from the discussion about doing an IDL based vmstate
description.
Regards,
Anthony Liguori
>
> Thanks, Juan.
>
prev parent reply other threads:[~2011-11-15 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 17:44 [Qemu-devel] KVM call agenda for November 15th Juan Quintela
2011-11-14 17:47 ` Anthony Liguori
2011-11-15 16:06 ` Anthony Liguori [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=4EC28E00.3050205@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).