Can we get stable patches in a digest mode?
From: Steven Rostedt
Date: Wed Nov 18 2026 - 10:13:11 EST
Hi,
With all the AI patches that have been coming my way where I apply them and
they have a Cc to stable a new issue has arose. As AI finds bugs from the
beginning of time (when the code was first introduced decades ago) these
patches are applicable to go back through all the currently maintained
stable releases.
Each release a patch is backported to will be emailed out. Thus, if you
have a fix that affects all stable releases, you will get an email for each
of those releases:
5.10, 5.15, 6.1, 6.6, 6.12, 6.18, 7.3
That is 7 emails for a single fix that went upstream. When I have 20 AI
fixes of old code, that means I'm likely to get 140 emails for them. To
make matters worse, some of these fixes will have dependency patches that
get backported as well, and I get emailed on those too!
I actually like to know what patches are being backported to stable. But
honestly, I don't care which stables they are being backported to. It would
be really nice to have a way to say "this patch is being backported to
these stable releases" and not a separate email for each release.
Now I want to say I really appreciate the time that Greg and Sasha spend on
doing these backports, and I hate to ask them to do any more work than they
already do. But because I get so many emails for stable backports I tend to
ignore all of them as there are too many of them to see if there is an
issue where one of them should not be backported.
Yesterday I added a filter to simply filter out the stable patches into
their own folder, but that means I'm pretty much guaranteed to ignore them
completely.
Does anyone else have any ideas on how to improve the situation without
causing too much work for anyone?
Thanks,
-- Steve