From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Proposed 2.4 release schedule (softfreeze 16th June)
Date: Tue, 9 Jun 2015 19:06:12 +0100 [thread overview]
Message-ID: <CAFEAcA_UwRyQHB3_WPRsABBPknMcGPL9P2DsERxgc2fy27NMeg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_2kZ=G2bfjsOK6=L9Q+pyDRKOdWjPfbqm4JO8C=na_MQ@mail.gmail.com>
On 26 May 2015 at 15:44, Peter Maydell <peter.maydell@linaro.org> wrote:
> As usual, schedule is at:
> http://wiki.qemu.org/Planning/2.4
>
> Note that softfreeze is in three weeks time!
>
> Please let me know if you have any suggestions or objections
> to this proposed timescale -- the conference dates mean the
> we're a bit restricted, but I think this should work OK.
I took the silence as enthusiastic acceptance, so I have
removed the "draft" note from the wiki page. Softfreeze is
now a week away!
-- PMM
prev parent reply other threads:[~2015-06-09 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 14:44 [Qemu-devel] Proposed 2.4 release schedule (softfreeze 16th June) Peter Maydell
2015-06-09 18:06 ` 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=CAFEAcA_UwRyQHB3_WPRsABBPknMcGPL9P2DsERxgc2fy27NMeg@mail.gmail.com \
--to=peter.maydell@linaro.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).