From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Joe Perches <joe@perches.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tracking MAINTAINERS versus tracking SUBSYSTEMS
Date: Sun, 19 Aug 2007 08:22:18 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708190818280.7224@localhost.localdomain> (raw)
In-Reply-To: <1187483578.4200.51.camel@localhost>
On Sat, 18 Aug 2007, Joe Perches wrote:
> 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?
i'm confused -- i thought that was sort of the whole purpose of this
exercise, to match parts of the kernel source tree against the
maintainer for those parts, and to do that via the defined
"subsystem" which is currently used in MAINTAINERS.
you can, of course, banish the concept of a subsystem entirely and
work purely from a file and directory perspective, but i think the
notion of the kernel tree being composed of subsystems is a useful
idea. that's just my opinion, though.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-08-19 12:30 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
2007-08-19 12:22 ` Robert P. J. Day [this message]
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=Pine.LNX.4.64.0708190818280.7224@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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