He enjoys playing with language. Perhaps that term tickled his fancy over carefully phrased cussing. Either that or he wants to reserve the swear jar for NVIDIA.
It's a bug alright - in the kernel. How long have you been a maintainer? And you *still* haven't learnt the first rule of kernel maintenance?
If a change results in user programs breaking, it's a bug in the kernel. We never EVER blame the user programs. How hard can this be to understand?
Shut up, Linus. And I don't _ever_ want to hear that kind of obvious garbage and idiocy from a kernel maintainer again. Seriously.
WE DO NOT BREAK USERSPACE!
Seriously. How hard is this rule to understand? We particularly don't break user space with TOTAL CRAP. I'm angry, because your kernel was so _horribly_ wrong, and the patch that broke things was so obviously crap. The whole patch is incredibly broken shit.
Fix your f*cking kernel, because it is obviously broken. And fix your approach to kernel programming.
It's not as funny when you have to explain it. I guess there are a lot of people who don't recognize my post.
For those who don't know, my "Linus, SHUT THE FUCK UP" comment was a word-for-word copy (with the name changed) of one of Linus's earlier and more famous rants [slashdot.org] at a poor hapless kernel developer. He had been doing that privately for years, but that was one of the first times he did it on a public mailing list and it made news. It actually got a lot worse since then, but that was one of the most fam
double ungood (Score:0, Troll)
Or creative (Score:2)
Perhaps we should be telling Linus... (Score:3, Insightful)
Linus, SHUT THE FUCK UP!
It's a bug alright - in the kernel. How long have you been a maintainer? And you *still* haven't learnt the first rule of kernel maintenance?
If a change results in user programs breaking, it's a bug in the kernel. We never EVER blame the user programs. How hard can this be to understand?
Shut up, Linus. And I don't _ever_ want to hear that kind of obvious garbage and idiocy from a kernel maintainer again. Seriously.
WE DO NOT BREAK USERSPACE!
Seriously. How hard is this rule to understand? We particularly don't break user space with TOTAL CRAP. I'm angry, because your kernel was so _horribly_ wrong, and the patch that broke things was so obviously crap. The whole patch is incredibly broken shit.
Fix your f*cking kernel, because it is obviously broken. And fix your approach to kernel programming.
Re: Perhaps we should be telling Linus... (Score:1)
Re: Perhaps we should be telling Linus... (Score:3)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
It's not as funny when you have to explain it. I guess there are a lot of people who don't recognize my post.
For those who don't know, my "Linus, SHUT THE FUCK UP" comment was a word-for-word copy (with the name changed) of one of Linus's earlier and more famous rants [slashdot.org] at a poor hapless kernel developer. He had been doing that privately for years, but that was one of the first times he did it on a public mailing list and it made news. It actually got a lot worse since then, but that was one of the most fam
Re: (Score:2)
To me it should have been modded funny. Where did people's sense of humor go ?
In anycase glad this was modded up
Re: Perhaps we should be telling Linus... (Score:2)
Re: (Score:2)