lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 9 Jul 2009 16:08:10 +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 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.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ