Calling other people’s work “garbage” is not conclusive proof of arrogance, if that work is actual garbage. Linus has calmed down a lot over the years, yet at this point if he still has issues with somebody’s work, it’s probably best to listen rather than calling that arrogance.
Personally, I do believe the quality of Linux kernel has a lot to do with having a steward able to be firm and opinionated, rather than adopting a passive anglo management style where confrontation is avoided at all costs.
And critique of the work is expected when the quality of the work is the question. But all the problems here are about conduct, which doesn't seem to get through.
I think OP is expecting that to be the outcome, given the roughly 2/3rds "Kent is (insert insinuation)" vs the 1/3rd "your stuff works, please stick around".
I worked for a guy that was looking forward to this work five years ago for a business product need. I'm glad to see it's made some headway in that time, but I have to wonder what it'd take to salvage the introduction of it to the Linux public at large. How do you even reset this mess?
I think nothing will happen, and Linus himself will eventually be whipped into place. Kent has come a long way in terms of communications, and all this talk about preserving sacrament of "collaborative community of kernel dev" reads real rich. The fact of the matter: bcachefs is the only modern + reliable filesystem in Linux right now. To throw it out—is madness, frankly. git rm -rf would be a show of weakness... basically telling everybody that they don't care about technical merit anymore. But really nothing will happen because Linus will eventually get whipped into place. The software is too good for this petty trickery to take place.
If the filesystem corrupts data, it has to be fixed at the maintainer's discretion. This is what the users want. Tough luck it makes Linus' life harder! Not to mention that he's allowed btrfs to run unchecked for so long. Kent put it nice, actually, kernel work is not about pleasing egos of top guys; it's about delivering software for users:
> "Work as service to others" is something I think worth thinking about. We're not supposed to be in this for ourselves; I don't write code to stroke my own ego, I do it to be useful. I honestly can't even remember the last time I wrote code purely for enjoyment, or worked on a project because it was what I wanted to work on. My life consists of writing code base on what's needed; to fix a bug, to incorporate a good idea someone else had, to smooth something over to make someone else's life easier down the line. Very rarely does it come from my own vision. My feelings are entirely secondary to the work I do.
> If the filesystem corrupts data, it has to be fixed at the maintainer's discretion. This is what the users want. Tough luck it makes Linus' life harder!
Where do you get this idea? Lots of Linux users want lots of things - a big part of the reason Linux is so successful is because they don't get what they want, and the project instead focuses on stable development and release cycles. Many users want Linux to break userspace in this or that case. Do you think Linus should do that, because it's what the users want?
And lets not forget we're talking about an experimental filesystem. If you decide to use one of those, it's not asking too much of you to compile your own kernel.
Funny, because "don't break userspace" is one of the principles I've been citing.
Things always degenerate when it turns into power struggles and people are going "No, I decide!".
"Make sure thinks work" is the underlying principle, and it's based on that that the code should have been, and was merged.
But then the personality conflicts and power struggles came out, and there's no need for that.
- You don't go overriding a subsystem maintainer without a clear justification; if the patch in question has a good reason for being there and can't affect the rest of the kernel, there's a really high bar to clear. This has been an issue for the XFS folks in the past.
- We have to be able to have technical and policy discussions without it degenerating into "I don't trust you and you need therapy". That's just childish. The private discussions got really ugly on this one.
And, regarding bcachefs still being marked as experimental: I'm being much more conservative with the experimental label than btrfs or ext4 were. Your data is safer on bcachefs than btrfs, today: you're not going to lose a filesystem, repair is thorough and robust and complete.
You may still hit hiccups, which is why the experimental label is there, but robust and complete repair and rock solid multi device have been reason enough for a lot of people to switch already.
Well, he already lost T'so, and I recall he's pretty high-up on the command chain. This appears to not be about technical merit anymore, vs existing as a "co-worker" with other kernel peers.
>And now, I just got an email from Linus saying "we're now talking about git rm -rf in 6.18", after previously saying we just needed a go-between.
Edit to add that LWN noted this at the end of the "The rest of the 6.17 merge window" post[1].
[0]: https://lwn.net/ml/all/5ip2wzfo32zs7uznaunpqj2bjmz3log4yrrde...
[1]: https://lwn.net/SubscriberLink/1032095/06b4e3b1b30fe2a9/