[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090710184409.GB4136@sirena.org.uk>
Date: Fri, 10 Jul 2009 19:44:09 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Joe Perches <joe@...ches.com>
Cc: Pekka Enberg <penberg@...helsinki.fi>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@...r.kernel.org
On Fri, Jul 10, 2009 at 09:25:00AM -0700, Joe Perches wrote:
> On Fri, 2009-07-10 at 14:17 +0100, Mark Brown wrote:
> > That seems reasonably effective with 5% or so as the default. I do
> > think the default should be non-zero if we're going to be encouraging
> > people to use this as standard, though.
> I'm not sure minimization of maintainers in
> the result is that desirable but I am for
> figuring out what works best.
It's not so much minimising maintainers per se that I'm concerned about
as ensuring that people doing general cleanup work don't end up getting
CCed on lots of random stuff, partly for their benefit and partly to
make get_maintainers easier to use.
> What have you experimented with and how have the
> results changed?
A combination of patches I'm working on and source files in subsystems I
maintain (basically, stuff where I know off the top of my head who
should turn up). The noticable issues are things like Jean Delvare
turning up for sound/soc/codecs/tlv320aic3x.c as a result of kernel wide
API update work he was doing - by tweaking the percentage I was able to
get the output to exclude people who I know have done non-specific
cleanup work.
--
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