From: Stefan Weil <sw@weilnetz.de>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Last call for release-critical fixes for 2.12
Date: Tue, 17 Apr 2018 15:19:53 +0200 [thread overview]
Message-ID: <d002e4ff-e0c9-f66e-a25a-51605a79b55f@weilnetz.de> (raw)
In-Reply-To: <CAFEAcA-FaS+HeihGmbhrLAR8e=jmz-Og+OKGakGX7MGb_KgwCw@mail.gmail.com>
Am 17.04.2018 um 15:03 schrieb Peter Maydell:
> I'm planning to tag rc4 this afternoon (UK time), which I expect
> to be the last rc for the 2.12 series. This is your last chance
> to flag up anything we absolutely must fix for this release.
> Please reply to this email and also update
> https://wiki.qemu.org/Planning/2.12#Known_issues
> if there's anything we've missed.
>
> thanks
> -- PMM
Update po files? That's not a "must fix", but it would be nice to have
those files synchronized with ui/gtk.c again.
Regards
Stefan
next prev parent reply other threads:[~2018-04-17 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 13:03 [Qemu-devel] Last call for release-critical fixes for 2.12 Peter Maydell
2018-04-17 13:19 ` Stefan Weil [this message]
2018-04-17 13:40 ` Philippe Mathieu-Daudé
2018-04-17 13:50 ` Peter Maydell
2018-04-17 14:05 ` Stefan Weil
2018-04-17 14:15 ` Daniel P. Berrangé
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=d002e4ff-e0c9-f66e-a25a-51605a79b55f@weilnetz.de \
--to=sw@weilnetz.de \
--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).