From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Moving Hard Freeze to Monday, May 6th.
Date: Wed, 1 May 2013 18:51:06 +0100 [thread overview]
Message-ID: <CAFEAcA8eqLWs220_u7n3_zyei5qbXiLsL_TewJms08CpjcLxww@mail.gmail.com> (raw)
In-Reply-To: <87li7zj26g.fsf@codemonkey.ws>
On 30 April 2013 19:36, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
> The current release schedule has hard freeze happening tomorrow. There
> are a few things still outstanding including cpu hotplug and updating
> SeaBIOS. We still need to resolve how to handle the softfloat code
> too. I am particularly interested in this last one for the 1.5 release.
>
> Given this, I'd like to delay the Hard Freeze until Monday and slip the
> 1.5 release by two days to the 17th to ensure we have enough -rcs..
Fine by me, since I, er, forgot hardfreeze would be today :-)
-- PMM
prev parent reply other threads:[~2013-05-01 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 18:36 [Qemu-devel] [RFC] Moving Hard Freeze to Monday, May 6th Anthony Liguori
2013-05-01 16:24 ` Rob Landley
2013-05-03 12:33 ` Mark Cave-Ayland
2013-05-01 17:51 ` Peter Maydell [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=CAFEAcA8eqLWs220_u7n3_zyei5qbXiLsL_TewJms08CpjcLxww@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=anthony@codemonkey.ws \
--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).