Development statistics for the 5.0 kernel

Posted Feb 22, 2019 23:09 UTC (Fri) by martinfick (subscriber, #4455)
In reply to: Development statistics for the 5.0 kernel by neilbrown
Parent article: Development statistics for the 5.0 kernel

I believe it could be helpful if new code contributions were throttled by ensuring that a contributor's known bugs were fixed before accepting new contributions from them. This is a policy I try to enforce on my team. That would probably be hard to do privately.

to post comments

Development statistics for the 5.0 kernel

Posted Feb 23, 2019 8:24 UTC (Sat) by error27 (subscriber, #8346) [Link]

My impression is that this isn't really an issue in the kernel. Once you know the code at fault (and thus the author) then the fix is normally straight forward. The difficulty lies in figuring out which code is at fault.

The other issue in the kernel is that after two years the original author isn't around or doesn't want to fix bugs. I seldom bother reporting static analysis issues over two years old. If it's less than two years we are good at addressing those.

People take a lot of pride their work generally.