From: Randy Dunlap <rdunlap@xenotime.net>
To: Joe Perches <joe@perches.com>
Cc: Pavel Machek <pavel@suse.cz>, "H. Peter Anvin" <hpa@zytor.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Ben Dooks <ben-linux@fluff.org>,
Uwe Kleine-K?nig <ukleinek@strlen.de>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] List of maintainers (draft #3)
Date: Tue, 30 Sep 2008 17:35:12 -0700 [thread overview]
Message-ID: <20080930173512.c221ade7.rdunlap@xenotime.net> (raw)
In-Reply-To: <1222819790.29215.126.camel@localhost>
On Tue, 30 Sep 2008 17:09:50 -0700 Joe Perches wrote:
> On Tue, 2008-09-30 at 17:10 -0700, Randy Dunlap wrote:
> > On Mon, 29 Sep 2008 19:56:25 +0200 Pavel Machek wrote:
> > > Yes please. Manually searching MAINTAINERS is boring and hard... 'Is
> > > it NETWORK BLOCK DEVICE' or 'NBD'? 'ALSA' or 'ADVANCED LINUX SOUND
> > > SYSTEM'? ... plus if you want subsystem maintainer, search tends to
> > > give you about 179 individual driver maintainers, first.
> > Well.... both the acronym and long name should be listed IMO.
> > Especially the acronym/short name.
>
> Human based visual searches are error prone.
>
> There really does need to be some systematic and automated
> mechanism to find the maintainers for a particular file.
>
> Maintainer file patterns, either centralized in MAINTAINERS
> or distributed in some mechanism in the file system or git
> are useful.
>
> Linus' original point about "hotness" of MAINTAINERS being
> an issue was later refuted by Linus.
>
> http://lkml.org/lkml/2008/2/13/414
I just don't think that it's a big problem like you and Pavel seem to.
IOW I'll just disagree.
---
~Randy
next prev parent reply other threads:[~2008-10-01 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 14:54 Denis Vlasenko
2008-09-22 8:12 ` Uwe Kleine-König
2008-09-22 9:12 ` Ben Dooks
2008-09-22 9:23 ` Pekka Enberg
2008-09-22 16:40 ` H. Peter Anvin
2008-09-22 19:42 ` Uwe Kleine-König
2008-09-23 5:10 ` Joe Perches
2008-09-29 17:56 ` Pavel Machek
2008-10-01 0:10 ` Randy Dunlap
2008-10-01 0:09 ` Joe Perches
2008-10-01 0:35 ` Randy Dunlap [this message]
2008-10-01 13:36 ` Pavel Machek
2008-10-01 15:41 ` Randy Dunlap
2008-10-01 12:25 ` [PATCH] [RFC] Add a script that searched per-file maintainers for a patch Uwe Kleine-König
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=20080930173512.c221ade7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ben-linux@fluff.org \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=penberg@cs.helsinki.fi \
--cc=ukleinek@strlen.de \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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
all inboxes | Powered by JetHome®