> I'd add one level of abstraction: have each filename map to a "module" name.
> In this case, each filename relating to devfs would map to module "devfs";
> there would then be an entry mapping devfs <-> Richard.
> (Perhaps a hierarchy - fs.devfs - with people like Al listed for "fs"?)
Could work, but there are some bits that have no maintainer as such,
eg, the pci irq routing. There have been several interested parties
hacking on it however. A means of having people add themselves to the
list would be a 'must have' feature.
> It should be a little easier having a mapping to a module - in most cases,
> there's a clear "module" to which each file belongs. Then just track who's
> "subscribed to" that module...
Having a mapping from kernel source filename -> email address would
still be preferred personally.
$ cclist devfs
is really not much of an improvement over
$ grep -C3 -i devfs MAINTAINERS
Other than the addition of extra 'interested, cc me too' people.
The only problem with my original idea is that its a pita to keep
up to date. kernel files get added and removed on a weekly (sometimes
daily) basis. Whoever is dumb^Wwonderful enough to volunteer to
maintain such a database is likely to have their work cut out for
them, so maybe your module idea is preferable.
Hmmm..
Dave.
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs- 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/