kadup 33 points a year ago

path: 0 19343061, hotness: undefined, score: 33, children: 1

He is fine

A lot of the drama was stirred up by the media. Him and Linus are still on good terms. They both agreed that the current development pass is not compatible with Linux release cycles.

I also hope you aren't using bcachefs to store important data. It is still very new and shouldn't be relied apon

save

path: 0 19343061 19344219, hotness: undefined, score: -7, children: 0

just_another_person 1 point a year ago

This developer is just all kinds of wrong. I won't trust any of this code to store my data if a large group of other kernel developers have issues with it, and the process that goes into testing and committing it.

save

path: 0 19342878, hotness: undefined, score: 1, children: 14

ikidd 18 points a year ago

The code is fine, the LKML has nothing but good things to say about his skills, on this and other things he's worked on in the kernel. But his interpersonal skills and his ability to work inside the guidelines of how the kernel development process works is the shits.

save

path: 0 19342878 19342907, hotness: undefined, score: 18, children: 13

just_another_person -6 points a year ago

It's not fine. The code was rejected many times for being problematic, which is why the overall project ended up getting rejected from the kernel.

save

path: 0 19342878 19342907 19342957, hotness: undefined, score: -6, children: 12

ikidd 16 points a year ago

It was rejected for putting in features in bugfix only windows. It was always about how he reacted to issues like that which got him moved to "externally maintained" If you have examples of commits being rejected on their actual coding merits, please link.

save

path: 0 19342878 19342907 19342957 19343183, hotness: undefined, score: 16, children: 11

just_another_person -7 points a year ago

No. His code, testing methods, and submitting code that broke both testing and basic construct was the issue.

You can dance all day around the issue, but a developer who can't get a fairly simple bit of code in good enough order to submit for upstream, THEN can't even test to make sure it doesn't break AT, THEN N is also behind deadline, THENNNNN is also a huge dick about it...not a good developer.

All he had to do was not completely shit the bed, and he did it repeatedly. THOUSANDS of other developers interact with that same list and upstream code on a weekly basis. This guy's code and methods is shit, and deserved to have his code kicked out. He's a terrible developer, and I wouldn't trust his code to wipe with.

save

path: 0 19342878 19342907 19342957 19343183 19343537, hotness: undefined, score: -7, children: 10