> any given piece of code to identify the responsible maintainer.  The motivation
> for this proposal is that the present system, a single top-level MAINTAINERS
> file, doesn't seem to be scaling well.

It scales perfectly. Most of the people you annoyed are _in_ the maintainers
and credits file. The fundamental problem is identical regardless of what
you change - people forget to update things unless there is motivation [1]

Alan
[1] as proof of this claim count the number of CREDIT file updates made shortly
after the RH share offering..


_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel

Reply via email to