linux-kernel - RFHelp: Splitting MAINTAINERS into maintainers/* and Makefile/Kconfig support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1187297496.5906.113.camel@localhost>
Date:	Thu, 16 Aug 2007 13:51:36 -0700
From:	Joe Perches <joe@...ches.com>
To:	linux-kernel@...r.kernel.org
Subject: RFHelp:  Splitting MAINTAINERS into maintainers/* and
	Makefile/Kconfig support

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

So that distributions could continue to produce
a MAINTAINERS block if desired, how could
make be extended to produce such a file from
these individual blocks?

Maybe:
        "cat [0-9a-z]* > ../MAINTAINERS"?

Would it need to?

Anyone have suggestions for Makefile/Kconfig support?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/