Bcachefs Fixes Pull Once Again Frustrates Linus Torvalds - Two Choices Offered
Bcachefs Fixes Pull Once Again Frustrates Linus Torvalds - Two Choices Offered
Honestly, I am siding with Linus here. Mainline is not the place for last minute changes without testing. And it seems Kent isn't going to change his methods, etc. That and the retort was pretty disrespectful.
I have high hopes bcachefs can be something great but... At its current rate it's going to flame out before reaching its potential.
Super disrespectful! Is he seriously big-timing Linus?
If I'm Linus, i would have removed bcachefs from mainline already. From his reply he never once admit his attitude problem and keep thinking he is right.
This type of people can't work with others, not today, not in future.
I'm surprised Linus didn't remove it after the last time
If you're so convinced you know best, I invite you to start writing your own filesystem. Go for it.
Dude is seriously missing the point here. It's not about what, it's about how.
If the dude is so convinced he knows best, I invite him to write and manage his own kernel. Go for it. See how well your users like it when your slapdash execution breaks everything.
That arrogance and ignorance is just on another level.
Yah, I think this is just going to end up with it being cut. Thats fine, zfs does ok this way, I'm sure bcachefs will get on fine.
Speedrunning
RiserFSReiserFS again are we?I mean the sole developer of the FS's own actions sinking a meritorious piece of software.
Being an ass is different to being a murderer, but both are poor choices to make.
the guy's name was Reiser.
Bah, typo. I shall fix. TYVM.
He's not a murderer ... yet.
If he becomes one, I'll start having serious concerns about anyone developing a fs!
And before you start whining - again - about how you are fixing bugs, let me remind you about the build failures you had on big-endian machines because your patches had gotten ZERO testing outside your tree.
As far as I know, the Linux Foundation does not provide testing infrastructure to it's developers. Instead, corporations are expected to use their massive amount of resources to test patches across a variety of cases before contributing them.
Yes, I think Kent is in the wrong here. Yes, I think Kent should find a sponsor or something to help him with testing and making his development more stable (stable in the sense of fewer changes over time, rather than stable as in reliable).
But, I kinda dislike how the Linux Foundation has a sort of... corporate centric development. It results in frictions with individual developers, as shown here.
Over all of the people Linus has chewed out over the years, I always wonder how many of them were independent developers with few resources trying to figure things out on their own. I've always considered trying to learn to contribute, but the Linux kernel is massive. Combined with the programming pieces I would have to learn, as well as the infrastructure and ecosystem (mailing list, patch system, etc), it feels like it would be really infeasible to get into without some kind of mentor or dedicated teacher.
Testing infrastructure would help for sure, but it's not necessarily the lack of infra that's causing trouble.
Linus complains the author didn't submit the patch to some places for public comments and testing BEFORE requesting a merge.
It sounds like he expects something like
Here's a mailing list thread asking for feedback and testing. No one complained in a week, could you merge ?
Linus complains the author didn’t submit the patch to some places for public comments and testing BEFORE requesting a merge.
Although a reasonable expectation, I can't find anything about this on the kernel.org docs for posting patches. They seem to imply that you just check and verify your patch before submitting it on the kernel mailing list, but that's it. I didn't see any mentions of mailing lists explicitly for feedbacks or other conventions.
I thought it was about the previous time (was it in September?), but it already happened again? Linus really has a lot of patience now after working on his attitude, he's got my respect for it
[...]Linus really has a lot of patience [...]
Haha that was a good one
Christ. That response from Linus felt pretty fair, Kent seems kinda impossible to work with to be honest :/
Though I did appreciate someone else in this thread pointing out that he may not have the resources for testing. He still seems impossible to work with, but it's at least good to have context 😅