[RFC] is it time to split up the MAINTAINERS file?

From: Rob Landley
Date: Tue Jun 11 2013 - 00:49:20 EST

Quite possibly the answer is "no", but the MAINTAINERS file is approaching 10,000 lines. Getting a bit unwieldy.

Most of the entries look like:

M: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
L: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx (moderated for non-subscribers)
S: Maintained
F: arch/arm/mach-s5pv210/mach-aquila.c
F: arch/arm/mach-s5pv210/mach-goni.c
F: arch/arm/mach-exynos/mach-universal_c210.c
F: arch/arm/mach-exynos/mach-nuri.c

Which could be moved to an arch/arm/MAINTAINERS file, and the relevant paths trimmed.

The question is: would this be an improvement? (And worth the changes to checkpatch.pl and such required to make it work?)

One potential _advantage_ of this is we could make the reporting hierarchy more explicit. The first entry in arch/arm/MAINTAINERS would be the arm maintainer and everybody else _under_ there goes through him. (Also, that guy could handle updates to the local MAINTAINERS file itself, so we're not always spamming Andrew. Such updates could even post to the architecture-specific list rather than linux-kernel.)

Yeah, reality isn't neatly nested. Lots of things refer to include files and Documentation files, but there's generally a main area of focus (where's the actual _code_?), and when you do have something like:

M: Simon Horman <horms@xxxxxxxxxxxx>
M: Magnus Damm <magnus.damm@xxxxxxxxx>
L: linux-sh@xxxxxxxxxxxxxxx
W: http://oss.renesas.com
Q: http://patchwork.kernel.org/project/linux-sh/list/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
S: Supported
F: arch/arm/mach-shmobile/
F: drivers/sh/

You could either have the same entry in more than one MAINTAINERS file or keep it at a higher level. (This wouldn't eliminate the top level MAINTAINERS, merely trim it down a bit.)

Just throwing it out there. Seems like it might be a thing, someday anyway...

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