From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
devel@lists.libvirt.org,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>
Subject: Re: [PATCH 0/3] Remove deprecated machines pc-i440fx-2.4 up to pc-i440fx-2.12
Date: Fri, 17 Jan 2025 11:25:02 +0000 [thread overview]
Message-ID: <Z4o-DsOmfiKdnEkQ@redhat.com> (raw)
In-Reply-To: <9e64e7cf-eca9-4b9c-ba30-1ce1441e81f7@redhat.com>
On Fri, Jan 17, 2025 at 12:14:43PM +0100, Thomas Huth wrote:
> On 17/01/2025 12.07, Daniel P. Berrangé wrote:
> > On Fri, Jan 17, 2025 at 11:27:35AM +0100, Thomas Huth wrote:
> > > While our new auto-disablement of old machine types will only kick
> > > in with the next (v10.1) release, the pc-i440fx-2.* machine types
> > > have been explicitly marked as deprecated via our old deprecation
> > > policy mechanism before (two releases ago), so it should be fine to
> > > remove them now already.
> >
> > These were marked deprecated manually in 9.1.0 with:
> >
> > commit 792b4fdd4eb8197bd6eb9e80a1dfaf0cb3b54aeb
> > Author: Philippe Mathieu-Daudé <philmd@linaro.org>
> > Date: Wed Feb 28 10:34:35 2024 +0100
> >
> > hw/i386/pc: Deprecate 2.4 to 2.12 pc-i440fx machines
> > Similarly to the commit c7437f0ddb "docs/about: Mark the
> > old pc-i440fx-2.0 - 2.3 machine types as deprecated",
> > deprecate the 2.4 to 2.12 machines.
> >
> > but that commit was reverted a couple of weeks later in 9.1.0 dev
>
> No, we did not revert that commit, the text is still there, so I think it
> still applies.
Oh, you mean the text in deprecated.rst. I just reverted the manual
deprecation in the code.
> > when I added the automatic deprecation/deletion logic
> >
> > commit 37193b7b43b6a973e56fa115098c5895ebdc7145
> > Author: Daniel P. Berrangé <berrange@redhat.com>
> > Date: Thu Jun 20 17:57:41 2024 +0100
> >
> > hw/i386: remove obsolete manual deprecation reason string of i440fx machines
> >
> > IOW, in terms of releases, these deprecations were introduced under
> > the new policy rather than the old policy.
>
> Why should your generic policy override an explicit statement for those
> machines?
I guess that's matter of opinion. I considered the policy to apply to
all versioned machine types deprecated from 9.1.0 onwards. Having them
mentioned in deprecated.rst doesn't alter the policy, IMHO, it is merely
a bit of redundant documentation.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-01-17 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 10:27 [PATCH 0/3] Remove deprecated machines pc-i440fx-2.4 up to pc-i440fx-2.12 Thomas Huth
2025-01-17 10:27 ` [PATCH 1/3] tests/qtest/test-x86-cpuid-compat: Remove tests related to pc-i440fx-2.3 Thomas Huth
2025-01-17 12:12 ` Fabiano Rosas
2025-01-17 16:48 ` Philippe Mathieu-Daudé
2025-01-17 10:27 ` [PATCH 2/3] hw/i386/pc_piix: Remove pc-i440fx-2.4 up to pc-i440fx-2.12 Thomas Huth
2025-01-17 11:58 ` Kashyap Chamarthy
2025-01-17 16:52 ` Philippe Mathieu-Daudé
2025-01-17 10:27 ` [PATCH 3/3] tests/qtest/test-x86-cpuid-compat: Replaced the removed pc-i440fx-2.* machines Thomas Huth
2025-01-17 11:07 ` [PATCH 0/3] Remove deprecated machines pc-i440fx-2.4 up to pc-i440fx-2.12 Daniel P. Berrangé
2025-01-17 11:14 ` Thomas Huth
2025-01-17 11:25 ` Daniel P. Berrangé [this message]
2025-01-17 16:52 ` Philippe Mathieu-Daudé
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=Z4o-DsOmfiKdnEkQ@redhat.com \
--to=berrange@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=farosas@suse.de \
--cc=kchamart@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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.