From: Alexander Graf <agraf@suse.de>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call agenda for May 11
Date: Tue, 11 May 2010 15:50:32 +0200 [thread overview]
Message-ID: <4BE960A8.9070601@suse.de> (raw)
In-Reply-To: <20100511103816.1322e60d@redhat.com>
Luiz Capitulino wrote:
> On Mon, 10 May 2010 08:02:50 -0700
> Chris Wright <chrisw@redhat.com> wrote:
>
>
>> Please send in any agenda items you are interested in covering.
>>
>
> - Exposing named errno in QMP errors
>
- flush=on
Alex
next prev parent reply other threads:[~2010-05-11 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 15:02 [Qemu-devel] KVM call agenda for May 11 Chris Wright
2010-05-11 13:31 ` [Qemu-devel] " Chris Wright
2010-05-11 13:38 ` [Qemu-devel] " Luiz Capitulino
2010-05-11 13:50 ` Alexander Graf [this message]
2010-05-11 13:53 ` Luiz Capitulino
2010-05-11 13:57 ` Jes Sorensen
2010-05-11 14:01 ` Luiz Capitulino
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=4BE960A8.9070601@suse.de \
--to=agraf@suse.de \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).