←back to thread

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.303s | 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 #
Guvante ◴[05 Jul 25 07:19 UTC] No.44470736[source]▶
"Pull requests aren't the time to talk about this" is only ever correct if the next part of the sentence is "because we already agreed" or some such.

Otherwise that is a red flag. Like pull requests are when discussions are had...

replies(2): >>44471044 #>>44471422 #
1. cwillu ◴[05 Jul 25 08:23 UTC] No.44471044[source]▶
And the linux kernel project has a long-established process, which includes not routinely landing major features post-merge-window without having a discussion first.