[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080503143335.01b956f3.sfr@canb.auug.org.au>
Date: Sat, 3 May 2008 14:33:35 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Jeff Garzik <jeff@...zik.org>, linux-next@...r.kernel.org,
sfrench@...ibm.com, swhiteho@...hat.com, stefanr@...6.in-berlin.de,
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,
penberg@...helsinki.fi, clameter@....com, ezk@...sunysb.edu,
linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next
Hi Andrew,
On Fri, 2 May 2008 15:33:01 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Fri, 02 May 2008 18:20:26 -0400
> Jeff Garzik <jeff@...zik.org> wrote:
>
> > Andrew Morton wrote:
> > > (Jeff, git-libata-all is a pretty important one)
> >
> > libata-dev.git#NEXT is for linux-next, and libata-dev.git#ALL is for -mm
> >
> > Already taken care of.
>
> Oh. Something seems to have gone wrong then.
>
> Next/Trees has:
>
> libata git git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git#NEXT
>
> but:
>
> y:/usr/src/25> diffstat patches/linux-next.patch | grep /ata/
>
> There's nothing there?
This just means that everything that Jeff expected to go into 2.6.26 is
not in Linus' tree, right? And he hasn't moved his 2.6.27 expectations
into linux-next yet (after all we are still in the 2.6.26 merge window).
--
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