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: <20150408032227.GD21171@thunk.org>
Date:	Tue, 7 Apr 2015 23:22:27 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Richard Weinberger <richard.weinberger@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ingo Molnar <mingo@...nel.org>, Joe Perches <joe@...ches.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: about the flood of trivial patches and the Code of Conduct (was:
 Re: [PATCH 19/25] sched: Use bool function return values of true/false not
 1/0)

On Tue, Apr 07, 2015 at 01:32:12PM +0200, Peter Zijlstra wrote:
> > I propose to send all this stuff though the trivial tree such that maintainers
> > of other subsystems have less workload and newbies (which are supposed
> > to send such patches) know which tree they have to work against.
> > Let's have to well defined and ordered. :-)
> 
> As per the other branch of this tree; an emphatic NO to that. The
> trivial tree is not a backdoor to bypass maintainers. Actual code
> changes do not get to go through any tree but the maintainer tree unless
> explicitly ACKed.

Agreed, I don't want trivial patches to ext4 either (a) polluting my
inbox, or (b) sneaking in behind my back in the trivial tree.

Joe, please just stop the madness.

Thanks,

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