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]
Message-ID: <1446036370.2757.104.camel@perches.com>
Date:	Wed, 28 Oct 2015 05:46:10 -0700
From:	Joe Perches <joe@...ches.com>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Javier Martinez Canillas <javier@...hile0.org>,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Wolfram Sang <wsa@...-dreams.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Sebastian Reichel <sre@...nel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Chanwoo Choi <cw00.choi@...sung.com>,
	Mark Brown <broonie@...nel.org>,
	Ben Dooks <ben-linux@...ff.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag

On Wed, 2015-10-28 at 12:24 +0000, Lee Jones wrote:
> On Wed, 28 Oct 2015, Joe Perches wrote:
> > On Wed, 2015-10-28 at 12:14 +0000, Lee Jones wrote:
> > > Ah, but wait.  get_maintainer.pl *does* assume M means Maintainer
> > > doesn't it?
> > 
> > No, it looks at the "S:" line.
> 
> Right.  Then assumes because the driver is 'supported' or 'maintained'
> that the person(s) listed in M: must be the Supporter(s) or the
> Maintainer(s).

Yup, except "assumes" isn't correct.

It's your definition of maintainer that seems to be at odds
with what's otherwise apparently commonly accepted.

Any "M:" entry in a section where the "S:" line is maintained
or supported is generally classified as a maintainer too.

For instance: I think most accept that I am a maintainer of
get_maintainer.pl.

I wrote most of get_maintainer and I accept most but not all
patches to it by acking some and nacking or otherwise requesting
changes in others.  I do not upstream it.

I don't have a git tree at kernel.org and don't really need one.
I rarely send pull requests.  I generally upstream through
Andrew Morton and he uses quilt.  It's working well enough.

The kernel summit thread from last year that initiated the "R:"
line in MAINTAINERS was primarily focused on encouraging new
patch review and honoring those that already take time to review.

http://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-May/000764.html

Knock your self out about clarifying how process should work.
Generate consensus where necessary but don't try too hard.

It's working reasonably well right now.  Most people are able
to maintain sanity by ignoring what's unimportant to them.


--
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