Reiser4 and kernel inclusion
Posted Sep 22, 2005 17:09 UTC (Thu) by southey
In reply to: Reiser4 and kernel inclusion
Parent article: Reiser4 and kernel inclusion
My understanding of the kernel development (from reading) is that the kernel does not seem to discriminate between people but rather on the actual code quality. It has been very clear that bad code (really how the code affects the complete kernel) does not enter or stay in the kernel regardless of who wrote it.
I think that the other filesystems like JFS also went through the same process (relative to the state of the kernel) except that these ports than new filesystems. These also had to undergo some changes that the respective developers made. I recall similar issues to reiser4 for when reiser3 started to be merged but reiser4 changes appear to be more invasive.
As for the current status, I think (with no knowledge of kernels) that the apparent rigid criteria applied to reiser4 is no different than say the current criteria in the kernal for real-time linux. Okay, sure a major kernel developer is involved (perhaps that is what reiser4 lacks) in the real-time changes but not all the real-time changes have been merged, some were rejected. Often these changes involved major rewrites (like making the changes less invasive etc).
to post comments)