[...] let's make it clear: you have exactly two choices here:
(a) play better with others
(b) take your toy and go home
I've been following from the sidelines, keen to see how bcachefs pans out. When it got included in the mainline kernel I was hoping that was a sign it was soon time to give it a proper whirl.
Based on the recent kerfuffle though, it really seems like the better move is to just remove it from mainline until it's a lot more mature.
"frustrates Linus" is a bit of an understatement here, Linus is considering removing bcachefs from mainline.
If it's removed, I'm somewhat skeptical it can return once it's more mature. Kent seems to think that the problem is code maturity while Linus is making it clear that the problem is that Kent won't follow process and work with others. I don't think Kent's behavior will change as long as Kent is in charge of bcachefs no matter how mature the codebase gets.
[...] let's make it clear: you have exactly two choices here:
(a) play better with others
(b) take your toy and go home
I've been following from the sidelines, keen to see how bcachefs pans out. When it got included in the mainline kernel I was hoping that was a sign it was soon time to give it a proper whirl.
Based on the recent kerfuffle though, it really seems like the better move is to just remove it from mainline until it's a lot more mature.
"frustrates Linus" is a bit of an understatement here, Linus is considering removing bcachefs from mainline.
If it's removed, I'm somewhat skeptical it can return once it's more mature. Kent seems to think that the problem is code maturity while Linus is making it clear that the problem is that Kent won't follow process and work with others. I don't think Kent's behavior will change as long as Kent is in charge of bcachefs no matter how mature the codebase gets.
"If you're so convinced you know best, I invite you to start writing your own filesystem. Go for it." - Kent
[flagged]
[flagged]
[flagged]
[flagged]