linux-kernel - Re: linux-next: the purge :-)

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: <alpine.LFD.1.10.0805081152310.3318@apollo.tec.linutronix.de>
Date:	Thu, 8 May 2008 11:55:14 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	linux-next@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	Ingo Molnar <mingo@...e.hu>, Greg KH <greg@...ah.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: linux-next: the purge :-)

On Thu, 8 May 2008, Stephen Rothwell wrote:
> Hi all,
> 
> Having published my expectations of what should be in linux-next, I am
> no implementing what I think is what I said.  :-)
> 
> This is open to discussion (including suggestions about other trees).
> 
> The following trees are being excluded from today because I think that
> they contain changes that:
> 	- have not been published/reviewed/tested sufficiently
> 	- are not currently intended for 2.6.26 or 2.6.27.
> (not all reasons apply to all trees).  Please don't take offense, I am
> just trying to obey my own guidelines.
> 
> ldp
> x86_latest
> sched_latest
> 
> Ingo, I assume that things will migrate from {x86,sched} latest to
> for-akpm (for-next?) over time.

We are working on refactoring our x86 work flow. We'll give you
notice, when the dust of the demolition has settled.

Thanks,
	tglx
--
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/