From: "Alex Bennée" <alex.bennee@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-stable <qemu-stable@nongnu.org>,
Michael Roth <michael.roth@amd.com>,
qemu-devel@nongnu.org
Subject: Re: qemu 7.2 stable release, 2nd try
Date: Tue, 28 Mar 2023 16:28:27 +0100 [thread overview]
Message-ID: <87o7ocrj26.fsf@linaro.org> (raw)
In-Reply-To: <4e79a438-778b-877d-d3dc-ad05cbab88cc@msgid.tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> writes:
> Hi!
>
> After posting an RFC (due to me doing a stable release for the first time) and
> getting exactly 0 replies/comments, I'm a bit worried, - does this mean there's
> no interest in getting 7.2-stable out of the doors at all? :)
I'm interested - although Debian already has the "latest" stuff we need.
What do you need though, re-reviews or just simple Acked-by's for the
included patches?
>
> With 8.0 approaching rapidly, and with no other comments or new patches for
> -stable, let's make this official within a week from now, on Mar-29.
>
> It *feels* like quite some more changes should be picked too, but let's do
> *something* after all :)
>
> I still need some minor help with the final step, - pushing to main qemu git
> repo and running the whole testsuite before the actual release. Asking for
> push/commit access for that.
>
> Thanks,
>
> /mjt
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-03-28 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 8:16 qemu 7.2 stable release, 2nd try Michael Tokarev
2023-03-22 9:15 ` Thomas Huth
2023-03-28 15:28 ` Alex Bennée [this message]
2023-03-28 16:17 ` Philippe Mathieu-Daudé
2023-03-28 16:34 ` Michael Tokarev
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=87o7ocrj26.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=michael.roth@amd.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.