Re: [PATCH v2 0/2] migration: feature removals for 11.0

[Peter Xu <peterx@redhat.com>]

On Mon, Feb 23, 2026 at 10:00:12AM +0000, Daniel P. Berrangé wrote:
> On Thu, Feb 19, 2026 at 08:23:06AM +0100, Markus Armbruster wrote:
> > Peter Xu <peterx@redhat.com> writes:
> > > I don't know if that'll work because logically we can also copy anyone or
> > > lists only when sending patches (e.g. with "git send-email --cc")..
> > 
> > For what it's worth, scripts/get_maintainer.pl would have told us to cc:
> > libvirt with this line:
> > 
> >     devel@lists.libvirt.org (open list:Incompatible changes)
> > 
> > > For now, I'll just remember to always copy libvirt list on touching
> > > deprecation file.  My apologize if it caused any unwanted surprise.
> > 
> > We cannot and do not expect a patch submitter to know and remember
> > everything.  We rely on tooling and review to catch misses in time.
> > Doesn't always work, because nothing and nobody's perfect.
> 
> If any contributor is sending patches to QEMU, please don't use the raw
> 'git send-email' command directly. Instead use 'git-publish' which wraps
> 'send-email' with logic that automatically consults get_maintainer.pl.
> 
> This means you'll always CC the required people by default, and have
> to conciously make an effort to drop them from the CC list.

I am using git-publish, I found that it's because I have my own profile
setup so it didn't use the default profile provided in .gitpublish, which
offered cccmd=.

Now I've added that into my setup too, thanks for the suggestion.

-- 
Peter Xu