From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: KVM call agenda for August 31
Date: Tue, 31 Aug 2010 08:30:16 -0500 [thread overview]
Message-ID: <4C7D03E8.5040508@codemonkey.ws> (raw)
In-Reply-To: <4C7C9F76.8050309@redhat.com>
On 08/31/2010 01:21 AM, Avi Kivity wrote:
> On 08/31/2010 12:54 AM, Juan Quintela wrote:
>> Please send in any agenda items you are interested in covering.
>>
>
> zero (dot|point) thirteen schedule
-rc1 is tagged locally and undergoing regression testing. Once that
finishes (later today), I'll push and upload. Once it's announced (~24
hours later) we've got one week until 0.13.0 to bring in additional
stable fixes.
Regards,
Anthony Liguori
prev parent reply other threads:[~2010-08-31 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 21:54 [Qemu-devel] KVM call agenda for August 31 Juan Quintela
2010-08-30 22:36 ` [Qemu-devel] " Anthony Liguori
2010-08-31 6:21 ` Avi Kivity
2010-08-31 13:30 ` 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=4C7D03E8.5040508@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@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).