torballs
Kind of weird. Lead developer wanted to keep the filesystem working no matter what. Linus wanted compliance to the release schedule.
Lead developer couldn’t work well with others, is what it really comes down to. The kernel is run that way for a reason, and if the lead Dev just had some patience, it wouldn’t have ended this way.
Linus has more to worry about than a single experimental FS in a kernel that runs the world. Kent can go have his drama off by himself for a while.
Oh sure. But it seems like the proper response should have been to reject the last minute changes instead of breaking user space by throwing out an entire filesystem that has been in the kernel for 10 years.
It hasn’t been removed. They’re just not accepting patches like they do for maintained subsystems. What’s thrown out, exactly?
Also 10 years? No. Try less than 2. It was merged in Linux 6.7
When someone is persistently disruptive, you can choose to spend your days babysitting and correcting them, or you can accept that they are unwilling or unable to change, show them to the door, and reclaim your time.
Linus has been doing the former for quite a while. Looks like he has now moved on to the latter. Seems like the proper response to me.
10 years
I think that just shows that Linus has been admirably patient with Kent.
Besides this change not breaking user space, the “don’t break user space” rule has never meant that the kernel cannot drop support for file systems, devices, or even entire architectures
