And if someone previously uninvolved with your work showed up one day and dumped a few weeks of a teams work in your lap in one giant patch that affected most of your codebase, you'd say thanks and look to merging it in rather than talk about proper process?
Most projects have a process and gigantic monolithic patches that include entire new projects and "cleanup" updates to core all wrapped up in one are unmanaged and unmergable. It's for the sake of process.
Of course I'd prefer they work in a way which meshes with existing process, but I'm not going to act dismissive and sigh if someone goes another way. If someone removed the GIL from CPython and gave me a context diff, for one I would barely be able to read that format, but I'd find a way to make it work.
Pull requests are great, but it's not like someone couldn't apply the patch and give them a hand - earlier in the thread someone did just that.
Most projects have a process and gigantic monolithic patches that include entire new projects and "cleanup" updates to core all wrapped up in one are unmanaged and unmergable. It's for the sake of process.