From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Joe Perches <joe@perches.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tracking MAINTAINERS versus tracking SUBSYSTEMS
Date: Sun, 19 Aug 2007 22:10:27 +0200 [thread overview]
Message-ID: <m3y7g7gua4.fsf@maximus.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0708190818280.7224@localhost.localdomain> (Robert P. J. Day's message of "Sun, 19 Aug 2007 08:22:18 -0400 (EDT)")
"Robert P. J. Day" <rpjday@mindspring.com> writes:
> 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.
Obviously the concept of subsystems is the right one, except that
the subsystems aren't that well defined (or they are but not
for average kernel user) - thus "file masks".
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-08-19 20:11 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
2007-08-19 15:37 ` Joe Perches
2007-08-19 20:10 ` Krzysztof Halasa [this message]
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=m3y7g7gua4.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox