Jeff Garzik <jgarzik@mandrakesoft.com>:
> > OK, but knowing who considers themselves responsible for the
> > associated subsystem is what I need (and a couple of people have in
> > fact emailed me saying "that Config.in is mine").
>
> Over and above the people who e-mail you, a good method is to look at
> the naming of each drivers/* subdirectory, and see if you can match up a
> name with an entry in MAINTAINERS. For example ISDN matches up with
> drivers/isdn/Config.in, while drivers/net/Config.in and
> drivers/char/Config.in do not have MAINTAINER entries. No hard and fast
> rule for this sort of thing..
Did that. It's how I came up with the base list I posted for corrections.
-- <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a>"Among the many misdeeds of British rule in India, history will look upon the Act depriving a whole nation of arms as the blackest." -- Mohandas Ghandhi, An Autobiography, pg 446
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:28 EST