qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU trunk now in hardfreeze
Date: Thu, 6 Nov 2014 12:51:23 +0800	[thread overview]
Message-ID: <545AFE4B.30201@huawei.com> (raw)
In-Reply-To: <CAFEAcA8KTLddaRf7GF6ycb8UVNuLqjzVHiT8EX4j+X6n+EW9QQ@mail.gmail.com>

On 2014/11/5 23:32, Peter Maydell wrote:

> Hi; I've just tagged v2.2.0-rc0 in master, so we're now officially
> in hardfreeze, and only accepting bug fixes from here onward.
> Mike Roth should have the rc0 tarballs out sometime later today.
> 
> I've updated http://wiki.qemu.org/Planning/2.2 to list -rc dates;
> as usual, one a week, with the hope that -rc3 will be the final one
> with no changes between that and the release proper.
> 
> Please make sure you update the changelog at
> http://wiki.qemu.org/ChangeLog/2.2 with any interesting/important
> new features that got added in this release.
> 

Hi, Peter

I think the below feature should be added in 2.2 release.

-Boot Devices
Supporting dynamically modify boot order of guest, and assuring
taking effect after the guest rebooting.

Request for wiki account, please. Thanks!

Best regards,
-Gonglei

  reply	other threads:[~2014-11-06  4:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 15:32 [Qemu-devel] QEMU trunk now in hardfreeze Peter Maydell
2014-11-06  4:51 ` Gonglei [this message]
2014-11-06  5:01   ` Amos Kong
2014-11-06  6:03     ` Gonglei
2014-11-06 16:49   ` Stefan Hajnoczi
2014-11-06 17:26     ` Paolo Bonzini
2014-11-07  0:42       ` Gonglei
2014-11-17 16:25         ` Stefan Hajnoczi
2014-11-18  1:35           ` Gonglei
2014-11-09  9:43 ` Mark Cave-Ayland
2014-11-09 16:42   ` Peter Maydell
2014-11-09 16:45     ` Mark Cave-Ayland

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=545AFE4B.30201@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=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).