Sounds like a good idea; I'll give it a shot over the next few days, unless
someone already has one :)
> Imagine a patch against devfs..
>
> $ cclist my.devfs.patch.diff
> Richard Gooch <rgooch@atnf.csiro.au>
> Alexander Viro <viro@math.psu.edu>
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"?)
> This 'little black book of addresses' doesn't have to be anything
> wonderful, but its tedious work for someone to make the textfile
> mapping the various source files to email addresses.
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...
James.
-
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/