Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Friday April 04 2014, @07:48PM   Printer-friendly
from the never-one-to-stay-silent dept.

From an email from Linus Torvalds to GKH

"Greg just for your information, I will *not* be merging any code from Kay [Sievers] 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. This is relevant to you because I have seen you talk about the kdbus patches, and this is a heads-up that you need to keep them separate from other work. Let distributions merge it as they need to and maybe we can merge it once it has been proven to be stable by whatever distro that was willing to play games with the developers.

But I'm not willing to merge something where the maintainer is known to not care about bugs and regressions and then forces people in other projects to fix their project. Because I am *not* willing to take patches from people who don't clean up after their problems, and don't admit that it's their problem to fix."

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 5, Interesting) by tomtomtom on Friday April 04 2014, @10:09PM

    by tomtomtom (340) on Friday April 04 2014, @10:09PM (#26427)

    Following the threads, the ultimate origin of the bug is more illuminating than the attitude of systemd's developers here. The reason this bug happened is that apparently systemd is defaulting to stashing its early log messages in the kernel dmesg ring buffer using the /dev/kmsg interface. That is so incredibly stupid I don't even know what to say about it. The constant extension of systemd to do more and more things which have nothing to do with init was bad enough (udev, logging, dbus, etcd .... where does it end?). But it's just astounding that someone could think it was an even remotely sensible idea to put log messages there, let alone someone who is apparently in charge of a subsystem as important as this. That pretty much makes up my mind that I won't EVER be using systemd if I can help it (unless something drastic changes).

    Starting Score:    1  point
    Moderation   +4  
       Insightful=1, Interesting=2, Informative=1, Total=4
    Extra 'Interesting' Modifier   0  

    Total Score:   5  
  • (Score: 0) by Anonymous Coward on Friday April 04 2014, @10:50PM

    by Anonymous Coward on Friday April 04 2014, @10:50PM (#26438)

    Did you know systemd is the brainchild of the same guy who came up with pulseaudio?

    Even George W. Bush knows "Fool me - you can't get fooled again."