From: Andrew Morton <akpm@osdl.org>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC:PATCH 000/002] EXT3: cleanups in preparation for ext4 clone
Date: Fri, 8 Sep 2006 14:56:17 -0700 [thread overview]
Message-ID: <20060908145617.f0d0a32a.akpm@osdl.org> (raw)
In-Reply-To: <20060908213914.11498.3272.sendpatchset@kleikamp.austin.ibm.com>
On Fri, 8 Sep 2006 17:39:17 -0400
Dave Kleikamp <shaggy@austin.ibm.com> wrote:
> I'm working on rebasing Mingming's ext4 patches on the -mm tree, and have
> noticed a couple cleanups that would be nice to have in ext3 before the
> code diverges.
Good idea, thanks.
I'll try to get all pending ext3/jbd stuff flushed out for 2.6.19-rc1 and
then we can put a plug in it for a while, get the ext4 copy-n-paste sorted
out. I'd suggest we aim to do this on the day after 2.6.19-rc1 is tagged.
Or maybe -rc2. The road to 2.6.19-rc1 is going to be rough - there's an
unusually large amount of work pending, and there is an unusual (although
still small) amount of overlap between the subsystem trees which people
will need to sort out. Because of this I expect it will take us more than
the nominal two weeks to reach -rc1.
prev parent reply other threads:[~2006-09-08 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 21:39 [RFC:PATCH 000/002] EXT3: cleanups in preparation for ext4 clone Dave Kleikamp
2006-09-08 21:39 ` [RFC:PATCH 001/002] EXT3: More whitespace cleanups Dave Kleikamp
2006-09-08 21:39 ` [RFC:PATCH 002/002] EXT3: Fix sparse warnings Dave Kleikamp
2006-09-08 22:17 ` Alexey Dobriyan
2006-09-10 14:31 ` Dave Kleikamp
2006-09-08 21:56 ` Andrew Morton [this message]
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=20060908145617.f0d0a32a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
--cc=torvalds@osdl.org \
/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