From: Anthony Liguori <anthony@codemonkey.ws>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: qemu-devel@nongnu.org,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for April 26th
Date: Tue, 26 Apr 2011 08:09:30 -0500 [thread overview]
Message-ID: <4DB6C40A.8090904@codemonkey.ws> (raw)
In-Reply-To: <4DB6B0D9.2060702@redhat.com>
On 04/26/2011 06:47 AM, Jes Sorensen wrote:
> On 04/26/11 11:24, Juan Quintela wrote:
>>
>> Please, send in any agenda items you are interested in covering.
>>
>> From last week:
>> Tools for resource accounting the virtual machines.
>> Luis Antonio Galindo Castro (FunkyM0nk3y)<funkymonster@gmail.com>
>>
>
> - Status of glib tree - next steps?
I actually decided to just rewriting all of QEMU in Python and C++..
;-)
Regards,
Anthony Liguori
>
> Jes
>
>
next prev parent reply other threads:[~2011-04-26 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 9:24 [Qemu-devel] KVM call agenda for April 26th Juan Quintela
2011-04-26 11:47 ` Jes Sorensen
2011-04-26 13:09 ` Anthony Liguori [this message]
2011-04-26 14:05 ` Jes Sorensen
2011-04-26 12:55 ` Jan Kiszka
2011-04-26 13:11 ` Anthony Liguori
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=4DB6C40A.8090904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Jes.Sorensen@redhat.com \
--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).