Resigning my first attempt to get patches through the 2.2.x process, and revoking my ratification of a list of patches (e.g. -1 as had been applied, including my own submissions - I will revert in any case, where misordered.)
Proposing that we start with the same branch model as used on 2.4.x to get through too many many-year-old patches to idly browse through; replay these in mostly-sequential order, and bring 2.2.x up to 2.4.x in the affected areas of code, and finally this proposal suggests the same merge as was applied to 2.4.25 GA release, modulo all our new crazy APLOGNO fun.
There is not much to see here, other than to compare rev no's of what had been applied/proposed reverts to the list of patches on the 2.2.x merge branch... the interesting data is on that merge branch. But extensive testing against the resulting code is critical to our hope of offering a last 2.2.x release to close that chapter. TIA to each and everyone who assists!