From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
quintela@redhat.com, Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] QEMU 2.8 release approaching
Date: Thu, 1 Dec 2016 17:14:43 +0800 [thread overview]
Message-ID: <583FEA03.8050901@huawei.com> (raw)
In-Reply-To: <CAJSP0QXA3Qnb=ZeYo6uJLqPNWvP+_MkGrpRFFc2i4X1k5X6JCw@mail.gmail.com>
Cc: Juan Quintela <quintela@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>
Hi Stefan,
I have one, but I'm not quite sure．Anyway, we caught this bug in our test.
[PATCH] migration: re-active images when migration fails to complete
Thanks,
hailiang
On 2016/11/30 23:42, Stefan Hajnoczi wrote:
> Dear QEMU community,
> QEMU 2.8.0-rc3 will be tagged on December 6th. If there are no
> pending issues -rc3 will become the QEMU 2.8 final release on December
> 13th. Let's make this tag a good one!
>
> If you are currently looking into pending issues or have bug fixes
> needing attention from maintainers, please reply to this email.
>
> At this stage only critical bugs, regressions, and build breakage
> should hold up the release.
>
> Thanks,
> Stefan
>
>
>
prev parent reply other threads:[~2016-12-01 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 15:42 [Qemu-devel] QEMU 2.8 release approaching Stefan Hajnoczi
2016-11-30 20:10 ` Laszlo Ersek
2016-12-01 2:47 ` Gonglei (Arei)
2016-12-01 3:25 ` Peter Xu
2016-12-01 3:26 ` Michael S. Tsirkin
2016-12-01 9:04 ` Stefan Hajnoczi
2016-12-01 10:30 ` Gonglei (Arei)
2016-12-01 11:08 ` Stefan Hajnoczi
2016-12-01 9:14 ` Hailiang Zhang [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=583FEA03.8050901@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).