[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080506144318.5432cdcc.sfr@canb.auug.org.au>
Date: Tue, 6 May 2008 14:43:18 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Pekka Enberg" <penberg@...helsinki.fi>,
linux-next@...r.kernel.org, sfrench@...ibm.com,
swhiteho@...hat.com, stefanr@...6.in-berlin.de, jeff@...zik.org,
ralf@...ux-mips.org, drzeus-list@...eus.cx, jack@....cz,
cbou@...l.ru, jens.axboe@...cle.com, ericvh@...il.com,
wim@...ana.be, chris@...kel.net, nico@....org, clameter@....com,
ezk@...sunysb.edu, linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next
On Mon, 5 May 2008 11:31:28 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> So I'd suggest that you have a #for-next which contains material for 2.6.26
> and 2.6.27 and a #for-mm which contains material for 2.6.28+.
>
> Only problem is, I'd need to generate the #for-next -> #for-mm diff, and
> that particular git operation has been troublesome in the past.
Yeah, it is fine if one is a subset of the other but otherwise fraught
with danger.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists