From: Joe Perches <joe@perches.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tracking MAINTAINERS versus tracking SUBSYSTEMS
Date: Sat, 18 Aug 2007 17:32:58 -0700 [thread overview]
Message-ID: <1187483578.4200.51.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0708181311490.10387@localhost.localdomain>
On Sat, 2007-08-18 at 13:35 -0400, Robert P. J. Day wrote:
> $ show_subsystem drivers/bluetooth/bpa10x.c
> BLUETOOTH
"what's a subsystem"?
I'm not sure there is an appropriate definition.
If there is an appropriate definition, why
should anyone care what subsystem a particular
file is in?
> 1) it reduces the MAINTAINERS file back to what it should be in the
> first place -- a simple reference list of each kernel subsystem, and
> who's responsible for it, so that constant reshuffling of files or
> directories in a particular subsystem doesn't require constant
> updating of the MAINTAINERS file.
I'd still be happy if MAINTAINERS went away.
I'm not sure what good it does other than have
a link to mailing lists that otherwise might not
be CC'd on patches.
> thoughts?
For user submission of bug reports, perhaps it'd be
more useful to have a submitkernelbugreport script
and a network enabled "dispatch bug report" to
appropriate maintainers service.
Try something out and see what happens.
Good luck. Joe
next prev parent reply other threads:[~2007-08-19 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 17:35 tracking MAINTAINERS versus tracking SUBSYSTEMS Robert P. J. Day
2007-08-19 0:32 ` Joe Perches [this message]
2007-08-19 12:22 ` Robert P. J. Day
2007-08-19 15:37 ` Joe Perches
2007-08-19 20:10 ` Krzysztof Halasa
2007-08-20 19:31 ` Chris Snook
2007-08-20 19:46 ` Joe Perches
2007-08-21 19:22 ` Chris Snook
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=1187483578.4200.51.camel@localhost \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.