"You know, you really are supposed to understand the code you are modifying..."
"We have to rediscover our roots: 'release early, release often'."
"It's all just too damn subtle and clever. Something like this should not need to be that subtle."
"But hey, don't listen to me - I like C++, and approve of Java."
"There is a ton of evidence both in computing and outside of it which shows that poor security can be very much worse than no security at all. In particular stuff which makes users think they are secure but is worthless is very dangerous indeed."
"That's very nice, but ... what is it? It would be really helpful if each patch series came with some kind of description of what problem the patches try to solve and how it solves it :)"
"I don't think we little angels want to tread here."
"First attempt at git, so please pull carefully."
"I don't think there's any benefit to anyone for developers to hide their stuff on remote mailing lists. Copying lkml increases the chances that someone will spot a bug or some improvement and it generally keeps people informed as to what's going on. Yeah, 120,000 messages/year. But a lot of them are just noise. Patches are important."
"Frankly I don't care about apparmor, I don't see it as a serious project. Smack is kind of neat but looks like a nicer way to specify selinux rules."
"The fact is, security people *are* insane. You just argue all the time, instead of doing anything productive. So please don't include me in the Cc on your insane arguments - instead do something productive and I'm interested."
"It wouldn't be efficient for you to implement something new, only to have it criticized again. I'd suggest that you come up with a concrete design, describe to us what you propose to do and let's take it from there."