linux-kernel - Re: linux-next: Requirements and process

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: <20080506044846.GE4773@kroah.com>
Date:	Mon, 5 May 2008 21:48:46 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: Requirements and process

On Sat, May 03, 2008 at 03:45:42PM +1000, Stephen Rothwell wrote:
> I currently have 54 trees that (I assume) are of type 2 above:
> 
> driver-core	usb

Internally I have both of these trees split into "current" and "next"
sections, so that I know what to merge when.

If it would make things easier for you, I'd be glad to split both of
these trees up in such a manner to make it more visable.

Perhaps:
	driver-core-next
	usb-next
	driver-core
	usb

would be sufficient for you?

> And three trees that I am not sure about:
> 
> x86-latest	sched-latest	ldp

ldp you have properly named as something that will probably go into
next-next or most likely next-next-next, but does build and run properly
today, yet has work to go in the "must clean up this crap" arena.

thanks,

greg k-h
--
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/