"Eric S. Raymond" wrote:
>
> Jeff Garzik <jgarzik@mandrakesoft.com>:
> > There are no configuration file maintainers generally. For major
> > subsystems, like drivers/char or drivers/net, it is -incorrect- to say
> > that there is a maintainer at all. For specific subsystems, like ISDN
> > or FireWire, the maintainers for those subsystems are the ones who
> > typically update the Config.in file, but that is not a rule. Andrezj
> > (sp?) in particular has been going through the Config.in files and
> > cleaning up a lot of cruft.
>
> 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..
Jeff
-- Jeff Garzik | Liberty is always dangerous, but Building 1024 | it is the safest thing we have. MandrakeSoft, Inc. | -- Harry Emerson Fosdick- 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:27 EST