From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
"quintela@redhat.com" <quintela@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for Septemebre 13
Date: Mon, 12 Sep 2011 08:17:42 -0500 [thread overview]
Message-ID: <4E6E0676.80602@codemonkey.ws> (raw)
In-Reply-To: <4E6E05DC.7090600@siemens.com>
On 09/12/2011 08:15 AM, Jan Kiszka wrote:
> On 2011-09-12 15:12, Anthony Liguori wrote:
>> On 09/12/2011 08:07 AM, Juan Quintela wrote:
>>> Hi
>>>
>>> Please send in any agenda items you are interested in covering.
>>
>> - Device state visualization
>
> Wow, still that controversial?
No, I just wanted to chat about different methods for moving forward.
Doing OTP is a bit easier than having a 30 email long thread :-)
Regards,
Anthony Liguori
>
> Reminds me that you asked me for some visitor adaption I haven't looked
> into yet...
>
> Jan
>
prev parent reply other threads:[~2011-09-12 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 13:07 [Qemu-devel] KVM call agenda for Septemebre 13 Juan Quintela
2011-09-12 13:12 ` Anthony Liguori
2011-09-12 13:15 ` Jan Kiszka
2011-09-12 13:17 ` 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=4E6E0676.80602@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.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).