[krnlthrway]

Did we read the same thread?

Kent sends commits last minute and his response is “they sat in my tree the last 2 weeks; nbd!”

Complains he has no idea what Linus is asking for…

He seems so overwhelmed a simple ask like “don’t let patches sit two weeks so you can personally noodle to your hearts content the git log” are missed.

Have seen similar from Kent on various kernel mailing threads I watch. Lots of deflection of his obligation to test more broadly, push sooner as he appeals to some big picture only he understands like he did here invoking acts over 20 years ago.

So what he’s working hard in his little btrfs bubble; what’s trickled down hill on others smells of bio waste

[klyrs]

We read the same thread. I haven't read all the context. Thanks for that.

But I disagree that he's deflecting his obligation to test more broadly -- it does sound like he's trying to get people together to do exactly that. It's easy to see this situation in black and white, and Linus's approach to the conversation is rather polarizing in that regard.

[vilanye]

He is deflecting the obligations that having a project in the kernel mainline puts on him.

Linus' reaction is very appropriate because Kent is breaking the mainline and wrecking the kernel development cycle. It is more than appropriate to pull bcachefs out of the mainline.

[ramon156]

I partly posted this to see if anyone had more context or experience with Kent. Thanks for the extra bit of information.

I can agree with both, but in the end it's Linus' decision.