What he meant was that instead of committing the changes you could have done the same as OverJoy, build a beta with your changes and make some select people test it out. When you're sure everything is done, you could commit the changes.
The way I see it though, I kinda understand that you'd want to commit after so much work in case some new revision changed something and you had to review your code again or stuff like that. But if that was the case and you were going to commit an "incomplete" or "not fully tested" change, you should have commented your new lines and leave the original code as it was.
If you did it like that, you'd be letting other devs know that there was some work in progress being done and they'd either skip over your code or warn you if something in it would be affected by changes they made; and the Wii U users wouldn't be having issues right now.
Of course it all comes down to whether you wanted it to be tested or not, and you're free to ignore this post since it's just me voicing my opinion. I've tested the rev and it works for me, but I have a Wii and a HID controller, so the issue can be either exclusive to the Wii U, or due to the kind of controller they're using.