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 Tuesday 13
Date: Mon, 12 Dec 2011 17:31:43 -0600 [thread overview]
Message-ID: <4EE68EDF.8030700@codemonkey.ws> (raw)
In-Reply-To: <874nx54bza.fsf@trasno.mitica>
On 12/12/2011 05:16 PM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
- QOM merge plan
I'd also like to do a code walk through of QOM at the first call of the new year.
Regards,
Anthony Liguori
>
> Thanks, Juan.
>
next prev parent reply other threads:[~2011-12-12 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 23:16 [Qemu-devel] KVM call agenda for Tuesday 13 Juan Quintela
2011-12-12 23:31 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-12 12:40 Juan Quintela
2012-03-13 0:22 ` Andreas Färber
2012-03-13 2:04 ` Anthony Liguori
2012-03-13 14:05 ` Andreas Färber
2012-03-13 13:31 ` Eduardo Habkost
2012-03-13 13:54 ` Michael S. Tsirkin
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=4EE68EDF.8030700@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).