From: Markus Armbruster <armbru@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: "Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org, "Juraj Marcin" <jmarcin@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Prasad Pandit" <ppandit@redhat.com>
Subject: Re: [PATCH v2 0/2] migration: feature removals for 11.0
Date: Tue, 17 Feb 2026 12:25:20 +0100 [thread overview]
Message-ID: <87ms17lihr.fsf@pond.sub.org> (raw)
In-Reply-To: <aZQ0q2r6w3OkSP2f@angien.pipo.sk> (Peter Krempa's message of "Tue, 17 Feb 2026 10:29:38 +0100")
Peter Krempa <pkrempa@redhat.com> writes:
> On Thu, Jan 15, 2026 at 17:55:01 -0500, Peter Xu wrote:
>> v2:
>> - Added R-bs
>> - Updated description for removing zero-blocks [Markus]
>> - Squashed the "fd: to file" test removal into the 2nd patch
>> - I dropped the COLO patch, I have a local patch to remove colo migration
>> completely, but looks like we won't do it.. Let's leave it for later but
>> do the rest first
>>
>> This series removes two deprecated features for 11.0.
>>
>> Please review, thanks.
>>
>> Peter Xu (2):
>> migration: Remove zero-blocks capability
>> migration: Remove fd: support on files
>>
>> docs/about/deprecated.rst | 20 -------------
>
> Note that per the 'MAINTAINERS' file, changes to any deprecations ought
> to be CC'd to the libvirt list for visibility.
>
> In this case we've forgotten about the deprecation and didn't fix it
> before the qemu cahnge was pushed. I'll send out patches soon, but keep
> in mind to *always* CC the libvirt list with deprecations.
Review fail (mine).
Should we try to make checkpatch.pl catch it? So far, it doesn't check
cc: at all.
next prev parent reply other threads:[~2026-02-17 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 22:55 [PATCH v2 0/2] migration: feature removals for 11.0 Peter Xu
2026-01-15 22:55 ` [PATCH v2 1/2] migration: Remove zero-blocks capability Peter Xu
2026-01-16 8:49 ` Markus Armbruster
2026-01-15 22:55 ` [PATCH v2 2/2] migration: Remove fd: support on files Peter Xu
2026-02-17 9:29 ` [PATCH v2 0/2] migration: feature removals for 11.0 Peter Krempa
2026-02-17 9:47 ` Daniel P. Berrangé
2026-02-17 9:55 ` Peter Krempa
2026-02-17 10:08 ` Daniel P. Berrangé
2026-02-17 11:25 ` Markus Armbruster [this message]
2026-02-18 21:21 ` Peter Xu
2026-02-19 7:23 ` Markus Armbruster
2026-02-23 10:00 ` Daniel P. Berrangé
2026-02-23 15:56 ` Peter Xu
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=87ms17lihr.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=peterx@redhat.com \
--cc=pkrempa@redhat.com \
--cc=ppandit@redhat.com \
--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 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.