From: Luiz Capitulino <lcapitulino@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM Call agenda for July 6th
Date: Mon, 5 Jul 2010 11:05:42 -0300 [thread overview]
Message-ID: <20100705110542.5d98c2ee@redhat.com> (raw)
In-Reply-To: <m3630uxfks.fsf@trasno.mitica>
On Mon, 05 Jul 2010 14:45:23 +0200
Juan Quintela <quintela@redhat.com> wrote:
>
> Please send in any agenda items you are interested in covering.
- 0.13 release
next prev parent reply other threads:[~2010-07-05 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 12:45 [Qemu-devel] KVM Call agenda for July 6th Juan Quintela
2010-07-05 14:05 ` Luiz Capitulino [this message]
2010-07-06 4:52 ` Alex Williamson
2010-07-06 13:26 ` Anthony Liguori
2010-07-06 13:53 ` Alex Williamson
2010-07-06 13:26 ` Anthony Liguori
2010-07-06 13:37 ` Kevin Wolf
2010-07-06 13:53 ` Anthony Liguori
2010-07-06 14:04 ` Kevin Wolf
2010-07-06 15:19 ` Markus Armbruster
2010-07-06 15:27 ` Kevin Wolf
2010-07-06 15:33 ` Anthony Liguori
2010-07-06 13:28 ` [Qemu-devel] " 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=20100705110542.5d98c2ee@redhat.com \
--to=lcapitulino@redhat.com \
--cc=chrisw@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).