@kurushimi@cm0002 From what I understand, Kent Overstreet has attempted to circumvent the release cycle by adding #features to an #RC, which was the final straw. #Linus (Torvalds) has warned him repeatedly, but it wasn’t just him. Based on a comment I read from one of the #kernel#developers, his repeated #antics made it considerably more #difficult for them to complete their #work. So while #technically you might be right, it’s not that simple.
Yep the maintainer repeated threw in stuff late in the release cycle . Here’s one instance
The clash stems from a long‑standing debate on kernel rhythm: Linus enforces strict release-cycle discipline, allowing only minimal fixes during release candidates.
At the same time, Kent submitted substantive changes (a patch implementing the new “journal_rewind” feature, which lets the entire filesystem be reset to an earlier point in time) justified by urgent data-recovery needs, though they landed late in the cycle.
@kurushimi @cm0002 From what I understand, Kent Overstreet has attempted to circumvent the release cycle by adding #features to an #RC, which was the final straw. #Linus (Torvalds) has warned him repeatedly, but it wasn’t just him. Based on a comment I read from one of the #kernel #developers, his repeated #antics made it considerably more #difficult for them to complete their #work. So while #technically you might be right, it’s not that simple.
Yep the maintainer repeated threw in stuff late in the release cycle . Here’s one instance