> And FYI, code gets changed by maintainers without discussion all the time. Whenever there's a merge conflict between trees is one example.
Except this was a controversial change that was NACKed previously. Slipping trivial changes and merge conflict resolutions in without review is one thing. Slipping a change that has been previously NACKed by other maintainers is something completely different.