There is in this case, and why Linus did accept the patch in the end. Previous cases less so though which is why Linus is so pissed at this one.
The reason for this new feature is to help fix data loss on users systems - which is a fine line between a bug and a new feature really. There is precedent for this type on thing in RC releases from other filesystems as well. So the issue in this instance is a lot less black and white.
The problem is that kent is a bullshitter and acted like he doesnt get what a feature freeze is.
If he cant communicate with linus as to why his patch is actually bugfix then he cant contribute to the kernel.
Honestly, not even in this case (especially given the history). Kent has a kernel tree people can pull if they need to. If it is an emergency, point people there.
There is in this case, and why Linus did accept the patch in the end. Previous cases less so though which is why Linus is so pissed at this one.
The reason for this new feature is to help fix data loss on users systems - which is a fine line between a bug and a new feature really. There is precedent for this type on thing in RC releases from other filesystems as well. So the issue in this instance is a lot less black and white.
That doesn’t excuse previous behaviour though.
The problem is that kent is a bullshitter and acted like he doesnt get what a feature freeze is. If he cant communicate with linus as to why his patch is actually bugfix then he cant contribute to the kernel.
Honestly, not even in this case (especially given the history). Kent has a kernel tree people can pull if they need to. If it is an emergency, point people there.