From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jbd/jbd2 NULL noise
Date: Fri, 28 Mar 2008 22:33:10 -0700 [thread overview]
Message-ID: <20080328223310.9a677e70.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080329045634.GM10722@ZenIV.linux.org.uk>
On Sat, 29 Mar 2008 04:56:34 +0000 Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Fri, Mar 28, 2008 at 09:01:52PM -0700, Harvey Harrison wrote:
> > > > > I did, it went into -mm and on Mar 5 it was taken into the subsystem
> > >
> > > Al, still morbidly curious about the akpm's scripts and aforementioned
> > > message...
> >
> > Not sure which tree, but received this on Feb 27:
> >
> >
> > The patch titled
> > jbd2: sparse warnings in revoke.c, journal.c
> > has been removed from the -mm tree. Its filename was
> > jbd2-sparse-warnings-in-revokec-journalc.patch
> >
> > This patch was dropped because it was merged into mainline or a
> > subsystem tree
> >
> > The current -mm tree may be found at
> > http://userweb.kernel.org/~akpm/mmotm/
>
> Ah... jbd part of it is still there, jbd2 is *also* there, but it's got
> ext4-mm- prefix to filename. And looking at ext4.git, jbd2 side of that
> stuff *is* merged, so what the hell is it doing in a separate file?
> Looks like -mm has ext4 stuff not as a single patch (like it does for
> many other git trees) but split into individual changesets for some
> reason...
>
Yup, -mm consists of
- 71 git trees (origin.patch plus 70 git-foo.patch) (some may be empty)
- The URL for each of these can be obtained from the first line of
git-foo.patch, in http://userweb.kernel.org/~akpm/mmotm/
- Nine quilt trees, pulled from various opendirs
Sekkrit locations:
http://ozlabs.org/~rusty/kernel/rr-latest
http://www.kernel.org/pub/linux/kernel/people/kristen/pci-hotplug
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver-core
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-usb
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-pci
http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/
http://kernel.org/pub/linux/kernel/people/bart/pata-2.6/patches/
ftp://ftp.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/
- squillions of other patches which are only in -mm.
Interesting factoid: -mm's series file was started on 1 Dec 2002 and is at
its 16,231st revision. I'm surprised it hasn't worn out.
next prev parent reply other threads:[~2008-03-29 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 3:07 [PATCH] jbd/jbd2 NULL noise Al Viro
2008-03-29 3:15 ` Harvey Harrison
2008-03-29 3:18 ` Al Viro
2008-03-29 3:26 ` Harvey Harrison
2008-03-29 3:42 ` Al Viro
2008-03-29 3:54 ` Al Viro
2008-03-29 4:01 ` Harvey Harrison
2008-03-29 4:56 ` Al Viro
2008-03-29 5:12 ` Harvey Harrison
2008-03-29 5:33 ` Andrew Morton [this message]
2008-03-29 5:25 ` Andrew Morton
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=20080328223310.9a677e70.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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