4 ms·
"Key, I'm fcking tired of the fact that you don't fix problems in the code you* write, so that the kernel then has to work around the problems you cause[...]I w
by Torgo 12y ago
"Key, I'm fcking tired of the fact that you don't fix problems in the code you* write, so that the kernel then has to work around the problems you cause[...]I will not be merging any code from Kay into the kernel until this constant pattern is fixed.[...]This has been going on for years, and doesn't seem to be getting any better."
That name sounds familiar.
https://bugs.freedesktop.org/show_bug.cgi?id=76935 https://bugs.freedesktop.org/show_bug.cgi?id=76935
https://plus.google.com/+gregkroahhartman/posts/Kd57G8s1cTD https://plus.google.com/+gregkroahhartman/posts/Kd57G8s1cTD
"What I mind is people closing bugs and not admitting mistakes. If Kay had even said "sorry, the excessive output was a bug in systemd, it's already fixed in current -git", that would have been a valid reason to close the bug. And for the people thinking this is a storm in a teacup: this is not the first time Kay has done this, which is why I personally get so frustrated. Kay has done the exact same thing with major bugs that were not fixed anywhere else, and that caused machines to fail at boot time, and Kay happily pointed the finger elsewhere for months at a time and closed bugzilla entries.
[...]
people are (I think) understandably upset that systemd not only screwed up, but then the people involved weren't even willing to say "sorry" about it but instead go "uh, it wasn't our bug, deal with it".
- digi_owl 12y agoMakes one wonder if Sievers should be allowed to touch any more projects...