Bcachefs may be headed out of the kernel

(lwn.net)

144 points ksec | 1 comments | 04 Jul 25 13:32 UTC | HN request time: 0.225s | source

Show context

criticalfault ◴[04 Jul 25 17:57 UTC] No.44466573[source]▶

I've been following this for a while now.

Kent is in the wrong. Having a lead position in development I would kick Kent of the team.

One thing is to challenge things. What Kent is doing is something completely different. It is obvious he introduced a feature, not only a Bugfix.

If the rules are set in a way that rc1+ gets only Bugfixes, then this is absolutely clear what happens with the feature. Tolerating this once or twice is ok, but Kent is doing this all the time, testing Linus.

Linus is absolutely in the right to kick this out and it's Kent's fault if he does so.

replies(8): >>44466668 #>>44467387 #>>44467968 #>>44468790 #>>44468966 #>>44469158 #>>44470642 #>>44470736 #

eviks ◴[05 Jul 25 06:57 UTC] No.44470642[source]▶

>>44466573 #

> One thing is to challenge things. > If the rules are set in a way that rc1+ gets only Bugfixes

So it's not ok to challenge things like the substance of rules...

replies(2): >>44470715 #>>44471323 #

1. yxhuvud ◴[05 Jul 25 09:21 UTC] No.44471323[source]▶

>>44470642 #

You don't challenge them by pretending they don't exist. That only make you look like an asshole.

The proper way here would have been two pull requests, one with all the bugfixes, and one with the new feature with a cover letter motivating why an exception should happen. And if this happens often enough with sufficiently good backing motivations, then he may be able to convince people.

↑