From: Joe Perches <joe@perches.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Chris Snook <csnook@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: RFHelp: Splitting MAINTAINERS into maintainers/* and Makefile/Kconfig support
Date: Fri, 17 Aug 2007 08:13:27 -0700 [thread overview]
Message-ID: <1187363607.822.88.camel@localhost> (raw)
In-Reply-To: <20070817144827.GB20963@uranus.ravnborg.org>
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@linuxtr.net
L: netdev@vger.kernel.org
W: http://www.linuxtr.net
S: Maintained
F: drivers/net/tokenring/3c359*
3C505 NETWORK DRIVER
P: Philip Blundell
M: philb@gnu.org
L: netdev@vger.kernel.org
S: Maintained
F: drivers/net/3c505*
[...]
would become
File "maintainers/3c359_network_driver" with content:
3C359 NETWORK DRIVER
P: Mike Phillips
M: mikep@linuxtr.net
L: netdev@vger.kernel.org
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@gnu.org
L: netdev@vger.kernel.org
S: Maintained
F: drivers/net/3c505*
thanks, Joe
prev parent reply other threads:[~2007-08-17 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 20:51 RFHelp: Splitting MAINTAINERS into maintainers/* and Makefile/Kconfig support Joe Perches
2007-08-17 6:25 ` Chris Snook
2007-08-17 12:30 ` Joe Perches
2007-08-17 14:48 ` Sam Ravnborg
2007-08-17 15:13 ` Joe Perches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187363607.822.88.camel@localhost \
--to=joe@perches.com \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox