I really didn't see anything wrong in his previous email about not enabling drivers by default for no good reason... If he has to repeat himself every merge window that's not getting angry for no good reason, that's merely being human and getting angry for a completely justified reason.
As for dealing with it, the way would do it would be to revert the commit and then ask the responsible maintainer explain/justify why the driver had to be turned off by default or if it was a mistake and then post a fixed update. The thing about naming and shaming is that it actually works surprisingly well and with the Linux kernel you can't even make the argument of "It scares off new developers" as blame travels up the hierarchy and as a result the targets of Linus' ire are the people best equipped to deal with it, i.e senior maintainers.
As someone who thinks that Linux's anger management hiatus was unnecessary I will admit that just blowing up at someone isn't the most effective way to deal with people making the same mistakes or just plain refusing to learn from them, but only because naming and shaming is so much more effective.
As for dealing with it, the way would do it would be to revert the commit and then ask the responsible maintainer explain/justify why the driver had to be turned off by default or if it was a mistake and then post a fixed update. The thing about naming and shaming is that it actually works surprisingly well and with the Linux kernel you can't even make the argument of "It scares off new developers" as blame travels up the hierarchy and as a result the targets of Linus' ire are the people best equipped to deal with it, i.e senior maintainers.
As someone who thinks that Linux's anger management hiatus was unnecessary I will admit that just blowing up at someone isn't the most effective way to deal with people making the same mistakes or just plain refusing to learn from them, but only because naming and shaming is so much more effective.
Comment