Documenting kernel code provenance
Posted May 27, 2004 16:10 UTC (Thu) by iabervon
Parent article: Documenting kernel code provenance
One of the things that Linus mentioned later in the thread is that this system should also be helpful for tracking down the people who worked on some code that turns out to have technical rather than legal problems. Obviously, that's not the reason this was initially proposed, but this will provide exactly the list of people who should discuss cases in which a patch turns out to have problems, from the person who was having a problem that the patch solved through all of the people who looked at it, didn't have issues with it, and passed it on. There have been plenty of cases where a patch went it, people complained, and then nobody could figure out exactly who had had a problem and whether it could be fixed better.
to post comments)