Recent searches
Search options
The next instalment of Linus vs. Kent – and Linus seems to be on the edge:
"[…] I'm contemplating just removing #bcachefs entirely from the [#Linux #kernel] mainline tree. Because you show again and again that you have no interest in trying to make mainline work. […]"
For the full discussion, start here: https://lore.kernel.org/all/cphtxla2se4gavql3re5xju7mqxld4rp6q4wbqephb6by5ibfa@5myddcaxerpb/t/#m631c24cd07f5820a4cbff8f25dff1d1a0c3cf2e7 (the quote is from one of the later mails from Linus). #LinuxKernel
@kernellogger I really hope that Linus drops bcachefs. The FS and its concept are interesting but not worth dealing with the negativity of Kent.
When rightfully criticizing his behaviour, the first thing he does is shitting on btrfs (and its devs), even if the discussion is not technical.
yup; most people can live with a sneaky remark now and then, but it's way more then that what others have to ensure from Kent…
He also snuck in an mm change that got NACKed through his fucking tree (!) then got abusive when it was reverted.
I genuinely don't understand how on any level this is being tolerated. It sets such a bad example for shit people in the kernel 'hey I'm not as bad as Kent and he gets away with it' is a thing, and I don't like it.
mistakes happen, are pointed out, and then people should learn from it; if it turns out that's not the case, something has to be and hopefully will be done, but that take a day or two.
I think we already are in the "takes a day or two" stage here (I'm ignoring here that this was someone likely to happen given the history, as that is a different story…).
hail himThat wasn't a mistake it was an intentional attempt to get an mm change in around mm developers, and it was fucking outrageous.
He did the same with fs too... :) the mm one was far, far worse though as in actually a really bad change. AND he got a CoC violation on the thread for reverting it!
The guy to me is just a bully.