From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for July 26
Date: Mon, 25 Jul 2011 18:33:50 -0500 [thread overview]
Message-ID: <4E2DFD5E.2010000@codemonkey.ws> (raw)
In-Reply-To: <m3zkk2545y.fsf@neno.neno>
On 07/25/2011 06:30 PM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
1) Live migration; see http://wiki.qemu.org/Features/Migration/Next or
ML thread
2) QEMU Object Model
3) 1.0 planning
Regards,
Anthony Liguori
>
> Later, Juan.
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-25 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 23:30 [Qemu-devel] KVM call agenda for July 26 Juan Quintela
2011-07-25 23:33 ` Anthony Liguori [this message]
2011-07-26 11:07 ` Stefan Hajnoczi
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=4E2DFD5E.2010000@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).