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: Re: [Qemu-devel] KVM call agenda for Feb 15
Date: Tue, 15 Feb 2011 16:03:17 +0200 [thread overview]
Message-ID: <4D5A87A5.9050507@redhat.com> (raw)
In-Reply-To: <4D5A8692.2020302@codemonkey.ws>
On 02/15/2011 03:58 PM, Anthony Liguori wrote:
> On 02/15/2011 04:44 AM, Avi Kivity wrote:
>> On 02/15/2011 12:18 AM, Anthony Liguori wrote:
>>> On 02/14/2011 11:56 AM, Chris Wright wrote:
>>>> Please send in any agenda items you are interested in covering.
>>>
>>> -rc2 is tagged and waiting for announcement. Please take a look at
>>> -rc2 and make sure there is nothing critical missing. Will tag
>>> 0.14.0 very late tomorrow but unless there's something critical,
>>> it'll be 0.14.0-rc2 with an updated version.
>>
>> Aren't you going to let users play with rc2 for a week or so? If
>> not, what's the point? just push out 0.14.0.
>
> If you think this is worth doing, we can try for 0.15.0. But this has
> been the plan for 0.14.0 and I'd like to stick to the plan (for a
> change) :-)
>
I'm fine either way. I just think it's strange to release an rc and a
.0 back to back.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-15 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 17:56 [Qemu-devel] KVM call agenda for Feb 15 Chris Wright
2011-02-14 19:54 ` Anthony Liguori
2011-02-15 12:11 ` Markus Armbruster
2011-02-15 14:00 ` Anthony Liguori
2011-02-15 13:42 ` Gleb Natapov
2011-02-14 22:18 ` Anthony Liguori
2011-02-15 10:37 ` Amit Shah
2011-02-15 10:44 ` Avi Kivity
2011-02-15 13:58 ` Anthony Liguori
2011-02-15 14:03 ` Avi Kivity [this message]
2011-02-15 16:03 ` Stefan Hajnoczi
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=4D5A87A5.9050507@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).