Bcachefs Fixes Pull Once Again Frustrates Linus Torvalds - Two Choices Offered

[Daktyl198]

In reality this entire thing is a diversion, what should really be discussed is why the flying fuck in 2024 (almost 2025), does Linux not have a nightly CI build against current in progress branch. This has been completely standard for open source projects for decades, and instead in their infinite wisdom Linux kernel dev's thought that offloading this to users wouldn't be problematic. My gosh.

Because pushing patches on a mailing list for Linus to pull into his own git tree is a fucking AWFUL way of doing software development and does not lend itself to using a CI at all. They'd have to move to a centralized hosted and managed git repo with CI integration (some form of GitHub/GitLab/etc) but all the old hats refuse to change the way they've developed software since the 70s. God forbid they learn any new processes in order to welcome way more developers, instead it's this extremely weird and hard to learn form of pushing patches where you have to do 5 hours of research just to know who to talk to about your 1 line patch instead of just submitting a PR and tagging it with the correct subsystem.

[Developer12]

I think you mixed something up here. You logically connected "a lot of people" with "big endian". Those two don't go together.

But as you most certainly read in the following discussion, they are discussing big endian ci. So it will get solved.

"so it will get solved" when he's finally called out on his bullshit.

These build failures are impacting enough people that Torvalds is perfectly willing to rip out the whole filesystem.

[oleid]

These build failures are impacting enough people that Torvalds is perfectly willing to rip out the whole filesystem.

They are nice to each other again. Please simply read the mailing list.

[PuckPoltergeist]

Hopefully, noone will get offended by what Kent wrote, as it is just his personal and professional opinion.
The kind of opinion which Kent is displaying demonstrates a commitment to correctness, reliability and robustness. That's what I appreciate.
I don't think he is boosting himself, I think that every other filesystem should also display such high standards of commitment to reliability.
The problem is that other filesystems (i.e. their devs) don't show such commitment. They don't take the user's data seriously enough. What I appreciate in Kent's mails, and what differentiates him from others, is commitment to important principles.

In my eyes it's offending to allege this, to say devs don't care about users data. They don't emphasize in every second sentence. It's just obviously that data integrity has the highest priority. And for me it's not professional to imply other devs don't care (like Kent does again and again). And that's about Josef mail.

[PuckPoltergeist]

Should perhaps re-read if that is your conclusion

Yes, please re-read

https://lore.kernel.org/linux-fsdevel/[email protected]/

[Mathias]

He didn't push patches with zero testing, stop spreading lies.

your patches had gotten ZERO testing outside your tree.

Literally read the article.

Literally read the article. Even Linus knows it had testing, just not outside his tree.

[User29]

But, only Kent is being crucified here. And, why?

It's easy to see the true answer: Kent is a single developer, while other Linux devs are backed by large corporations. So, they pick on Kent because his Bcachefs filesystem competes with theirs, and Kent is an easy target to pick.

Pls remove the tin foil hat Kent is not being chased by anyone. He just has a history of messing around and already made everyone (especially Linus) kind of edgy. I think that's understandable. And when the problem was pointed out, he started to attack people and processes and the technology/infra instead of saying "ok guys, sorry, I don't have access to BE systems, pls help me out". No, he picked up a fight instead and again.

[User29]

For the crucified-part:
https://lore.kernel.org/lkml/1728167...5377fdcdb8a198

Thanks for bringing this to light.
This clearly shows that Kent's "arguments" (booing btrfs, booing the rules, booing people, booing old times, trying to drag people down to the mud) is just imbecile and intolerable.

[flower]

Pls remove the tin foil hat Kent is not being chased by anyone. He just has a history of messing around and already made everyone (especially Linus) kind of edgy. I think that's understandable. And when the problem was pointed out, he started to attack people and processes and the technology/infra instead of saying "ok guys, sorry, I don't have access to BE systems, pls help me out". No, he picked up a fight instead and again.

well kent participated in linux for decades and only recently there seems to be that much drama. so something did change.
btw in this specific case it was linus that made a fight out of a small problem. i am not defending kents behavior. but in this case he didnt start the drama.

anyway it has been solved. the patches are merged and linus backed down.

[PuckPoltergeist]

Thanks for bringing this to light.
This clearly shows that Kent's "arguments" (booing btrfs, booing the rules, booing people, booing old times, trying to drag people down to the mud) is just imbecile and intolerable.

He can't stop it. He will continue throwing mud on others, believing he's the only one who is right and he has to save the world