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:	Sun, 8 Mar 2009 15:33:04 -0700
From:	Greg KH <greg@...ah.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	"Luis R. Rodriguez" <mcgrof@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jouni Malinen <j@...fi>, Sujith <m.sujith@...il.com>,
	Sujith <Sujith.Manoharan@...eros.com>,
	Senthilkumar Balasubramanian 
	<Senthilkumar.Balasubramanian@...eros.com>,
	"John W. Linville" <linville@...driver.com>,
	Christoph Hellwig <hch@...radead.org>,
	Vasanthakumar Thiagarajan <vasanth@...eros.com>
Subject: Re: Staging, place holder for better company/community development
	model

On Sun, Mar 08, 2009 at 01:07:45PM +0100, Johannes Berg wrote:
> On Mon, 2009-03-02 at 23:14 -0800, Luis R. Rodriguez wrote:
> 
> > If we should take this approach -- should we send patches for wireless
> > staging to John, or Greg? It would still be "crap" so I don't expect
> > John to accept to help maintain crap but what if its crap with a clear
> > defined path to un-crap land?
> 
> FWIW, I would MUCH prefer if the staging crap never passed any official
> mailing lists.

What do you mean by this?  You don't ever want to see any staging
patches on any mailing lists?  That doesn't sound helpful.

I can provide a simple procmail rule if you really don't like this kind
of thing, but that seems pretty extreme...
--
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