Messages in this thread | | | Date | Fri, 17 Aug 2007 02:25:03 -0400 | From | Chris Snook <> | Subject | Re: RFHelp: Splitting MAINTAINERS into maintainers/* and Makefile/Kconfig support |
| |
Joe Perches wrote: > I've got a tree with a directory full of separate > MAINTAINER blocks that looks like: > > 00_file_description > 3c359_network_driver > 3c505_network_driver > 3c59x_network_driver > 3cr990_network_driver > ... > zd1211rw_wireless_driver > zf_machz_watchdog > zr36067_video_for_linux_driver > zs_decstation_z85c30_serial_driver > zz_the_rest > > A little more than 600 files
NO. PLEASE!
The whole point of MAINTAINERS is to have one central repository for this information, instead of scattering it throughout the various source files. If that file is getting too unwieldy (and I don't think it is) then I could understand splitting it up hierarchically, for example having a drivers/net/MAINTAINERS that listed the info for all the net drivers.
What you're suggesting is a less efficient equivalent to putting the info directly into the source files. If that approach was enough to make people happy, we wouldn't have MAINTAINERS to begin with. Perhaps with a little automation it could be revived, though I think that adding a path pattern removes the need, while keeping it easier to parse by scripts.
I appreciate the effort to make MAINTAINERS more useful, but please don't add another 600 files to the tree.
-- Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |