From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: any remaining for-6.0 issues?
Date: Tue, 13 Apr 2021 06:38:32 +0200 [thread overview]
Message-ID: <87mtu223zr.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA8=qEFgvUqGFdWLJ+1ePPv2Ybisomrs2o77PyiAZA2sXg@mail.gmail.com> (Peter Maydell's message of "Mon, 12 Apr 2021 16:32:42 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> Last call to note anything we need to fix for 6.0 on
> https://wiki.qemu.org/Planning/6.0#Known_issues please.
Done for
[PATCH 0/1] sphinx: qapidoc: Wrap "If" section body in a paragraph node
I asked how to get it merged last week:
Message-ID: <87r1jmzb1n.fsf@dusky.pond.sub.org>
https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg00818.html
"In 6.1" is a valid, if sad answer.
> The schedule is to tag rc3 tomorrow, which I would ideally like
> to be the last rc before release. After rc3 I will only be taking
> fixes for bugs which are absolutely critical...
Understood.
next prev parent reply other threads:[~2021-04-13 4:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 15:32 any remaining for-6.0 issues? Peter Maydell
2021-04-12 18:44 ` Mark Cave-Ayland
2021-04-12 19:40 ` Peter Maydell
2021-04-12 21:13 ` Mark Cave-Ayland
2021-04-12 22:19 ` Mark Cave-Ayland
2021-04-13 4:38 ` Markus Armbruster [this message]
2021-04-13 5:56 ` Bin Meng
2021-04-13 6:19 ` Stefan Weil
2021-04-14 8:30 ` Bin Meng
2021-04-14 9:18 ` Stefan Weil
2021-04-14 9:34 ` Peter Maydell
2021-04-14 12:57 ` Bin Meng
2021-04-14 12:48 ` Thomas Huth
2021-04-14 13:57 ` Mark Cave-Ayland
2021-04-14 14:15 ` Mark Cave-Ayland
2021-04-14 14:36 ` Cornelia Huck
2021-04-14 16:26 ` Mark Cave-Ayland
2021-04-17 19:46 ` Peter Maydell
2021-04-18 10:38 ` Mark Cave-Ayland
2021-04-19 7:05 ` Cornelia Huck
2021-04-19 17:02 ` Cornelia Huck
2021-04-19 19:38 ` Mark Cave-Ayland
2021-04-20 9:58 ` Cornelia Huck
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=87mtu223zr.fsf@dusky.pond.sub.org \
--to=armbru@redhat.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).