Thanks, understood. I was optimizing for preserving the semantic contract, but I underweighted the permanent upstream maintenance cost. I'll keep these cases local unless a future regression shows they earn their place upstream.
I'll use git send-email next time. On Sat, 17 Oct 2026 11:55:26 -0400, Willem de Bruijn <[email protected]> wrote: > Megane Hebo wrote: > > Correction: Gmail Web rewrote tabs and wrapped some long lines in the > > inline diff I just sent, so that copy is not suitable for applying. > > > > The attached format-patch file is the authoritative byte-exact patch. > > Sorry for the transport noise. > > > > SHA256: cd11c3970f0a23ac039cdfcdc6338c20c79dbff3db8fdc93ea53b4b8996437b8 > > This is not the way to send patches > > https://docs.kernel.org/process/submitting-patches.html > > More in-depth: with AI it is easy to generate testcases. We now have > to consider which ones are important enough to submit. I think we all > have reproducers for these specific fixes offline. If we had thought > it worthwhile they would have been included in the feature series > itself.
