From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Feb 23
Date: Thu, 25 Feb 2010 09:49:13 +0200 [thread overview]
Message-ID: <4B862B79.309@redhat.com> (raw)
In-Reply-To: <4B854DA2.3080906@codemonkey.ws>
On 02/24/2010 06:02 PM, Anthony Liguori wrote:
> Hi Chris,
>
> On 02/22/2010 04:52 PM, Chris Wright wrote:
>> Please send in any agenda items you are interested in covering.
>
> I thought it might be easier to use the wiki for collecting agenda
> items instead of polling the list. It also us do a little bit more
> long term planning.
>
> http://www.linux-kvm.org/page/CommunityCall
>
Nice. But please use a non-ambiguous date format (this is about the
only place big endian makes sense).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-02-25 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 22:52 [Qemu-devel] KVM call agenda for Feb 23 Chris Wright
2010-02-24 16:02 ` [Qemu-devel] " Anthony Liguori
2010-02-25 7:49 ` Avi Kivity [this message]
2010-02-25 14:18 ` 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=4B862B79.309@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--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).