I don't agree with making direct personal criticisms towards people, but I think it's perfectly acceptable to be very blunt when responding to a bad idea (or patch, or whatever). In my own work I prefer blunt and honest feedback rather than attempts to avoid hurting my emotions. Of course it's always better if that criticism is combined with a constructive suggestions on how to fix the problem.
Honesty and courtesy are not mutually exclusive. "Github pull requests simply do not work for a project the size of the kernel" is terse, blunt, and still polite.
If that's true then fair enough, and I think your version of the comment is a nice middle ground.
I've never actually used github myself, and was only commenting on his tone of voice. If something is truly pure garbage, I think it should be said so, but I guess that's not the case here.
Unfortunately, this behavior is very well established. To take a few random examples of Linus calling people morons (and mentally diseased, etc) before this:
http://lists.gnu.org/archive/html/gnu-misc-discuss/2007-06/m... https://plus.google.com/102150693225130002912/posts/1vyfmNCY... http://yarchive.net/comp/linux/hibernation.html
https://lkml.org/lkml/2012/1/12/13
The point at issue here is not whether Linus is right. Of course he's probably right -- he's Linus. The question is whether he's being civil. In the case you're referring to, pirtlj's comment was also out of line (although ironically apt to this whole discussion). Linus however did not have to respond the way he did.
I'm convinced that's a fallacy.
Is "[Github's] pull requests and the online commit editing, are just pure garbage, go file a bug report with them" that much easier to voice than "[Github's] pull requests don't provide the flexibility or formatting we need for the kernel, so please read up on the proper pull request procedure. thanks!"? Plus such courtesy eliminates the inevitable outrage of the anti-prick crusade.