[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25564.1187035553@turing-police.cc.vt.edu>
Date: Mon, 13 Aug 2007 16:05:53 -0400
From: Valdis.Kletnieks@...edu
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: Satyam Sharma <satyam@...radead.org>,
Arjan van de Ven <arjan@...radead.org>,
Mariusz Kozlowski <m.kozlowski@...land.pl>,
Joe Perches <joe@...ches.com>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
On Mon, 13 Aug 2007 21:21:10 +0200, Jan Engelhardt said:
>
> On Aug 14 2007 00:02, Satyam Sharma wrote:
> >
> >Better solution is to have multiple MAINTAINERS files distributed in the
> >kernel tree, IMHO -- say a drivers/net/MAINTAINERS for maintainer info on
> >all various net drivers, drivers/kvm/MAINTAINERS for KVM maintainer info,
> >fs/ext3/MAINTAINERS for ext3 maintainers, fs/MAINTAINERS for generic VFS
> >maintainers info, so on and so forth. Of course, these individual
> >MAINTAINERS files could still have the newly-introduced "F:" fields as
> >well (drivers/net/MAINTAINERS would clearly require it, f.e.) ...
>
> Yes please.
>
> Or perhaps even putting the maintainer into the Kconfig files?
There's large swaths of code that don't have an obvious Kconfig entry
but do have a Maintainer entry - VFS, lots of kernel/*, and so on.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists