Hey,
Are you simply looking for a revert
Not of the whole commit. Just the wfDeprecated call.
I seem to remember that at one point the policy was to add a @deprecated tag, and then two releases later or so add the wfDeprecated call. Actually I made some commits which violated this policy and then got reverted.
With this approach extension authors can retain compatibility with the last few versions without doing ugly things and without running into piles of notices. Then when 1.25 comes they can do a search and replace and bump their min mw version to 1.23. That saves both the extension devs a lot of hassle, and does not throw the users of those extensions under the bus either.
Cheers
-- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3