linux-kernel - Re: git trees which are not yet in linux-next

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:	Mon, 5 May 2008 21:16:12 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	linux-next@...r.kernel.org, "Steven French" <sfrench@...ibm.com>,
	"Steven Whitehouse" <swhiteho@...hat.com>,
	"Stefan Richter" <stefanr@...6.in-berlin.de>,
	"Jeff Garzik" <jeff@...zik.org>,
	"Ralf Baechle" <ralf@...ux-mips.org>,
	"Pierre Ossman" <drzeus-list@...eus.cx>, "Jan Kara" <jack@....cz>,
	"Anton Vorontsov" <cbou@...l.ru>,
	"Jens Axboe" <jens.axboe@...cle.com>,
	"Eric Van Hensbergen" <ericvh@...il.com>,
	"Wim Van Sebroeck" <wim@...ana.be>,
	"Christian Zankel" <chris@...kel.net>,
	"Nicolas Pitre" <nico@....org>,
	"Christoph Lameter" <clameter@....com>,
	"Erez Zadok" <ezk@...sunysb.edu>, linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next

Hi Andrew,

On Sat, May 3, 2008 at 1:12 AM, Andrew Morton <akpm@...ux-foundation.org> wrote:
>  Guys, could you please prepare a tree for Stephen and send the details
>  over to him?  Please Cc me also.
>
>  Once this has happened, there should be no need to run a separate for-mm
>  branch.  I'll just switch over to using whatever branch linux-next is
>  using.

I was looking at preparing a for-next branch for the SLAB tree but I'm
not sure I understand the above. For something like the slab
allocator, you want as much exposure as possible before asking Linus
to pull so I would like to continue to (ab)use -mm for testing as
well. But that doesn't seem to fit the linux-next rules at all...

So what to do here? I don't have a problem with maintaining separate
branches for mm and next where the latter is not going to get much
action until very late in the release cycle when I'm preparing for the
next merge window.

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