From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-next@vger.kernel.org, sfrench@us.ibm.com,
swhiteho@redhat.com, stefanr@s5r6.in-berlin.de,
ralf@linux-mips.org, drzeus-list@drzeus.cx, jack@ucw.cz,
cbou@mail.ru, jens.axboe@oracle.com, ericvh@gmail.com,
wim@iguana.be, chris@zankel.net, nico@cam.org,
penberg@cs.helsinki.fi, clameter@sgi.com, ezk@cs.sunysb.edu,
linux-kernel@vger.kernel.org
Subject: Re: git trees which are not yet in linux-next
Date: Sat, 3 May 2008 14:33:35 +1000 [thread overview]
Message-ID: <20080503143335.01b956f3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080502153301.8b27ac31.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Hi Andrew,
On Fri, 2 May 2008 15:33:01 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 02 May 2008 18:20:26 -0400
> Jeff Garzik <jeff@garzik.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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-03 4:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 22:12 Andrew Morton
2008-05-02 22:20 ` Jeff Garzik
2008-05-02 22:33 ` Andrew Morton
2008-05-03 4:33 ` Stephen Rothwell [this message]
2008-05-03 4:54 ` Jeff Garzik
2008-05-02 22:42 ` Andrew Morton
2008-05-03 1:19 ` Stefan Richter
2008-05-03 1:34 ` Andrew Morton
2008-05-03 4:52 ` Jeff Garzik
2008-05-03 8:46 ` Stefan Richter
2008-05-05 0:18 ` Stephen Rothwell
2008-05-03 1:11 ` Stefan Richter
2008-05-03 1:18 ` Andrew Morton
2008-05-05 16:52 ` Liam Girdwood
2008-05-05 17:57 ` Andrew Morton
2008-05-06 4:45 ` Stephen Rothwell
2008-05-06 5:50 ` Andrew Morton
2008-05-06 7:18 ` Stephen Rothwell
2008-05-05 18:16 ` Pekka Enberg
2008-05-05 18:31 ` Andrew Morton
2008-05-05 18:41 ` Pekka J Enberg
2008-05-05 19:40 ` Stefan Richter
2008-05-05 21:11 ` Daniel Hazelton
2008-05-06 4:41 ` Stephen Rothwell
2008-05-06 4:43 ` Stephen Rothwell
2008-05-13 6:36 ` Pierre Ossman
2008-05-13 7:00 ` Stephen Rothwell
2008-05-13 10:47 ` Pierre Ossman
2008-05-13 12:33 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080503143335.01b956f3.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=cbou@mail.ru \
--cc=chris@zankel.net \
--cc=clameter@sgi.com \
--cc=drzeus-list@drzeus.cx \
--cc=ericvh@gmail.com \
--cc=ezk@cs.sunysb.edu \
--cc=jack@ucw.cz \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nico@cam.org \
--cc=penberg@cs.helsinki.fi \
--cc=ralf@linux-mips.org \
--cc=sfrench@us.ibm.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=swhiteho@redhat.com \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®