[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1222819790.29215.126.camel@localhost>
Date: Tue, 30 Sep 2008 17:09:50 -0700
From: Joe Perches <joe@...ches.com>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: Pavel Machek <pavel@...e.cz>, "H. Peter Anvin" <hpa@...or.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Ben Dooks <ben-linux@...ff.org>,
Uwe Kleine-K?nig <ukleinek@...len.de>,
Denis Vlasenko <vda@...t.imtp.ilyichevsk.odessa.ua>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] List of maintainers (draft #3)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists