Re: RFHelp: Splitting MAINTAINERS into maintainers/*and Makefile/Kconfig support

From: Joe Perches
Date: Fri Aug 17 2007 - 11:14:08 EST


On Fri, 2007-08-17 at 16:48 +0200, Sam Ravnborg wrote:
> Adding a specific target pà top-level Makefile is easy to
> do so I assume you are looking for something more advanced?

No, I'm looking for something simple.
Perhaps something like:

Makefile contents:

all: [0-9a-z]*

install:
sh cat [0-9a-z]* > ../MAINTAINERS

clean:
rm -f ../MAINTAINERS

I don't hardly understand the linux make machinery
for files that aren't .o, so I don't know if that's
reasonable or valid.

> And that part "more advanced" I do not know what is.
> Doing so using the normal kbuild machinery is not soo
> good since it will be parallel and we want something serail
> here.
>
> If you define how the Maintainer info is stored we can work
> out something.

My preference is for a single directory with
maintainers stored as separate files because
it's very simple, but it's still up in the air.

Basically breaking up the current monolithic
MAINTAINERS file into separate little files.

For instance this chunk of MAINTAINERS
[...]
3C359 NETWORK DRIVER
P: Mike Phillips
M: mikep@xxxxxxxxxxx
L: netdev@xxxxxxxxxxxxxxx
W: http://www.linuxtr.net
S: Maintained
F: drivers/net/tokenring/3c359*

3C505 NETWORK DRIVER
P: Philip Blundell
M: philb@xxxxxxx
L: netdev@xxxxxxxxxxxxxxx
S: Maintained
F: drivers/net/3c505*
[...]

would become

File "maintainers/3c359_network_driver" with content:
3C359 NETWORK DRIVER
P: Mike Phillips
M: mikep@xxxxxxxxxxx
L: netdev@xxxxxxxxxxxxxxx
W: http://www.linuxtr.net
S: Maintained
F: drivers/net/tokenring/3c359*

and

File "maintainers/3c505_network_driver" with content:
3C505 NETWORK DRIVER
P: Philip Blundell
M: philb@xxxxxxx
L: netdev@xxxxxxxxxxxxxxx
S: Maintained
F: drivers/net/3c505*

thanks, Joe

-
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/