From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 21th
Date: Tue, 21 Feb 2012 08:58:30 -0600 [thread overview]
Message-ID: <4F43B116.5090905@codemonkey.ws> (raw)
In-Reply-To: <4F43A4D4.7080408@redhat.com>
On 02/21/2012 08:06 AM, Kevin Wolf wrote:
> Am 20.02.2012 11:13, schrieb Juan Quintela:
>>
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> What's the status with qtest? (Though probably a one-line email would
> already answer this)
I still need to go through Paolo's patches. I'll make sure to look at them this
week to try to get something merged.
Regards,
Anthony Liguori
>
> Kevin
>
prev parent reply other threads:[~2012-02-21 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 10:13 [Qemu-devel] KVM call agenda for Tuesday 21th Juan Quintela
2012-02-21 14:06 ` Kevin Wolf
2012-02-21 14:49 ` Juan Quintela
2012-02-21 14:58 ` 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=4F43B116.5090905@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--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).