Stories
Slash Boxes
Comments

SoylentNews is people

Linus Blocks kdbus Code Merges from Kay Sievers

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

An anonymous coward writes:

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.
Linus Blocks kdbus Code Merges from Kay Sievers | Log In/Create an Account | Top | 72 comments | Search Discussion
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: 1) by jamesbond on Saturday April 05 2014, @05:04AM

    by jamesbond (2383) on Saturday April 05 2014, @05:04AM (#26551)

    The attitude seems to be pervasive in the systemd dev team. Look at another bug report linked from that LKML thread: https://bugs.freedesktop.org/show_bug.cgi?id=74589 [freedesktop.org]. Somebody reported that systemd won't work in under LXC (Linux OS-level virtualisation similar to OpenVZ/Virtuozzo); and the response is essentially "We don't use it that way, go fix it yourself." But because of this bug - you can't run *any* systemd-based OS under LXC virtualisation.

    This is not the only case, I found another one from systemd-udev (that I had to personally deal with) where compatibility-breaking change was announced for no good reason, with note that said change wasn't completed and there was no documentation around it, and 4 days later said change got committed *AND* at the same time dropping the code which worked for years and years on. It was rather easy to have both old and new code working at the same time but no, they had to drop it. In case you're wondering, I'm referring to this: http://lists.freedesktop.org/archives/systemd-deve l/2013-July/011773.html [freedesktop.org].