From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@xenotime.net>
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:09:50 -0700 [thread overview]
Message-ID: <1222819790.29215.126.camel@localhost> (raw)
In-Reply-To: <20080930171058.9e5f48d0.rdunlap@xenotime.net>
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
next prev parent reply other threads:[~2008-10-01 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 14:54 [RFC] List of maintainers (draft #3) 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 [this message]
2008-10-01 0:35 ` Randy Dunlap
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=1222819790.29215.126.camel@localhost \
--to=joe@perches.com \
--cc=ben-linux@fluff.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
--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