From: Michael Roth <michael.roth@amd.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: QEMU stable 7.2.1
Date: Thu, 6 Apr 2023 09:32:37 -0500 [thread overview]
Message-ID: <20230406143237.e6pc2g2zahwsw34j@amd.com> (raw)
In-Reply-To: <734b7b91-0305-1358-15f4-f63d7d272e7f@redhat.com>
On Thu, Apr 06, 2023 at 08:48:34AM +0200, Thomas Huth wrote:
> On 06/04/2023 08.33, Michael Tokarev wrote:
> > 06.04.2023 00:06, Michael Roth пишет:
> > ..
> > > Re-packaged tarball based on your 7.2.1 tag is now uploaded:
> > >
> > > https://www.qemu.org/download/
> >
> > Thank you Michael! Finally it's there :)
> >
> > There's one minor caveat still, though: it is missing in the
> > "Full list of releases" for whatever reason. Dunno how that
> > happened, maybe that page hasn't been (re)generated yet.
>
> FWIW, I can see it on https://download.qemu.org/ now.
>
> But there's another thing I noticed:
>
> On the homepage and on https://www.qemu.org/download/ the date of 7.2.1 is
> still the date of 7.2.0 (Mar 30th 2022) ... do we want to update this, or do
> we want to indicate the original release date of 7.2 there?
Thanks for the catch. The date should reflect the date the current
mainline/stable release was tagged, so I've updated it accordingly.
-Mike
>
> Thomas
>
>
prev parent reply other threads:[~2023-04-06 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 11:54 QEMU stable 7.2.1 Michael Tokarev
2023-04-05 13:58 ` Michael Roth via
2023-04-05 14:16 ` Michael Tokarev
2023-04-05 18:57 ` Michael Roth
2023-04-05 19:25 ` Peter Maydell
2023-04-05 21:06 ` Michael Roth
2023-04-06 6:33 ` Michael Tokarev
2023-04-06 6:48 ` Thomas Huth
2023-04-06 6:54 ` Michael Tokarev
2023-04-06 15:01 ` Michael Roth
2023-04-06 14:32 ` Michael Roth [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=20230406143237.e6pc2g2zahwsw34j@amd.com \
--to=michael.roth@amd.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@redhat.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).