All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 9 Jul 2009 16:08:10 +0100	[thread overview]
Message-ID: <20090709150810.GA25112@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1247151536.12426.39.camel@Joe-Laptop.home>

On Thu, Jul 09, 2009 at 07:58:56AM -0700, Joe Perches wrote:
> On Thu, 2009-07-09 at 10:30 +0100, Mark Brown wrote:

> > cleanups but have no specific interest in that area of code.  I think a
> > heuristic based on filtering the git log based on the proportion of
> > commits that were done by each committer would help with many of these
> > cases.

> git log "-by:" lines are already sorted by number of commits
> before selecting maintainers.  It doesn't matter if the
> line is acked-by:, Signed-off-by:, tested-by:, or
> brown-paper-bagged-by:, any "by:" signature is used.

Yup, I'm aware of that.

> I suppose when the number of committers returned by
> the "git log | grep" is low, returning just the 
> most frequent committers might be good.

> Any suggestions on better heuristics?

That's pretty much what I was thinking of too - tweaking the values for
the log queries based on the total number of hits so people only turn up
if they did a certain proportion of the commits.  It'd take some
experimentation to work out what the values to use should be, I guess.

  reply	other threads:[~2009-07-09 15:08 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 [this message]
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
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=20090709150810.GA25112@rakim.wolfsonmicro.main \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.