login
Header Space

 
 

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

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Andrew Morton <akpm@...>
Cc: <linux-next@...>, Steven French <sfrench@...>, Steven Whitehouse <swhiteho@...>, Stefan Richter <stefanr@...>, Jeff Garzik <jeff@...>, Ralf Baechle <ralf@...>, Pierre Ossman <drzeus-list@...>, Jan Kara <jack@...>, Anton Vorontsov <cbou@...>, Jens Axboe <jens.axboe@...>, Eric Van Hensbergen <ericvh@...>, Wim Van Sebroeck <wim@...>, Christian Zankel <chris@...>, Nicolas Pitre <nico@...>, Christoph Lameter <clameter@...>, Erez Zadok <ezk@...>, <linux-kernel@...>
Date: Monday, May 5, 2008 - 2:16 pm

Hi Andrew,

On Sat, May 3, 2008 at 1:12 AM, Andrew Morton <akpm@linux-foundation.org> wrote:

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
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 6:12 pm)
Re: git trees which are not yet in linux-next, Pierre Ossman, (Tue May 13, 2:36 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 13, 3:00 am)
Re: git trees which are not yet in linux-next, Pierre Ossman, (Tue May 13, 6:47 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 13, 8:33 am)
Re: git trees which are not yet in linux-next, Pekka Enberg, (Mon May 5, 2:16 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Mon May 5, 2:31 pm)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 12:43 am)
Re: git trees which are not yet in linux-next, Pekka J Enberg, (Mon May 5, 2:41 pm)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 12:41 am)
Re: git trees which are not yet in linux-next, Daniel Hazelton, (Mon May 5, 5:11 pm)
Re: git trees which are not yet in linux-next, Stefan Richter, (Mon May 5, 3:40 pm)
Re: git trees which are not yet in linux-next, Liam Girdwood, (Mon May 5, 12:52 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Mon May 5, 1:57 pm)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 12:45 am)
Re: git trees which are not yet in linux-next, Andrew Morton, (Tue May 6, 1:50 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 3:18 am)
Re: git trees which are not yet in linux-next, Stefan Richter, (Fri May 2, 9:11 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 9:18 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 6:42 pm)
Re: git trees which are not yet in linux-next, Stefan Richter, (Fri May 2, 9:19 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 9:34 pm)
Re: git trees which are not yet in linux-next, Jeff Garzik, (Sat May 3, 12:52 am)
Re: git trees which are not yet in linux-next, Stefan Richter, (Sat May 3, 4:46 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Sun May 4, 8:18 pm)
Re: git trees which are not yet in linux-next, Jeff Garzik, (Fri May 2, 6:20 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 6:33 pm)
Re: git trees which are not yet in linux-next, Jeff Garzik, (Sat May 3, 12:54 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Sat May 3, 12:33 am)
speck-geostationary