From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joe Perches <joe@perches.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@vger.kernel.org
Date: Fri, 10 Jul 2009 19:44:09 +0100 [thread overview]
Message-ID: <20090710184409.GB4136@sirena.org.uk> (raw)
In-Reply-To: <1247243100.11673.58.camel@Joe-Laptop.home>
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.
next prev parent reply other threads:[~2009-07-10 18:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 5:55 [PATCH 0/7] MAINTAINERS: cleanups Joe Perches
2009-07-08 5:55 ` [PATCH 1/7] MAINTAINERS: IA64 - pair P:/M: entries properly Joe Perches
2009-07-08 5:55 ` [PATCH 2/7] MAINTAINERS: Remove ivtv-user lists, add CX18 url Joe Perches
2009-07-08 5:55 ` [PATCH 3/7] MAINTAINERS: QLGE 10Gb ETHERNET - pair P:/M: entries properly Joe Perches
2009-07-08 5:55 ` [PATCH 4/7] MAINTAINERS: Use tabs in ACER ASPIRE ONE Joe Perches
2009-07-08 5:55 ` [PATCH 5/7] MAINTAINERS: Remove L: linux-kernel@vger.kernel.org Joe Perches
2009-07-08 6:32 ` Pekka Enberg
2009-07-08 6:39 ` Joe Perches
2009-07-08 6:44 ` Pekka Enberg
2009-07-08 6:47 ` Joe Perches
2009-07-08 6:55 ` Pekka Enberg
2009-07-08 16:37 ` Maciej W. Rozycki
2009-07-09 9:30 ` Mark Brown
2009-07-09 14:58 ` Joe Perches
2009-07-09 15:08 ` Mark Brown
2009-07-09 19:35 ` Joe Perches
2009-07-10 13:17 ` Mark Brown
2009-07-10 16:25 ` Joe Perches
2009-07-10 18:44 ` Mark Brown [this message]
2009-07-10 19:16 ` Joe Perches
2009-07-08 5:55 ` [PATCH 6/7] MAINTAINERS: Move ARPD to CREDITS Joe Perches
2009-07-08 5:55 ` [PATCH 7/7] MAINTAINERS: Update KERNEL JANITORS Joe Perches
2009-07-09 2:25 ` Randy Dunlap
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=20090710184409.GB4136@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
/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®