[lkml]   [2006]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/5] Forking ext4 filesystem and JBD2
On Thu, 10 Aug 2006 09:33:04 -0700
Mingming Cao <> wrote:

> Jeff Garzik wrote:
> > Mingming Cao wrote:
> >
> >> This series of patch forkes a new filesystem, ext4, from the current
> >> ext3 filesystem, as the code base to work on, for the big features such
> >> as extents and larger fs(48 bit blk number) support, per our discussion
> >> on lkml a few weeks ago.
> >
> > [...]
> >
> >> Any comments? Could we add ext4/jbd2 to mm tree for a wider testing?
> >
> >
> > ext4 developers should create a git tree with the consensus-accepted
> > patches.
> >
> > That way Linus can pull as soon as the merge window opens, Andrew is
> > guaranteed to have the latest in his -mm tree, and users and other
> > kernel hackers can easily follow the development without having to
> > gather scattered patches from lkml.
> >
> We do maintain a quilt(akpm) style patches on, the
> latest patches are always at
> We thought about doing git initially, still open for that doing do, if
> it's more preferable by Linus or Andrew. Just thought it's a lot
> easiler for non git user to pull the patches from a project website.

We should aim to get the big copy-ext3-to-ext4 patch into Linus's tree as
early as possible.

I'm just not sure when to do that. Immediately after 2.6.19-rc1 is
released would be good because it is when every tree (including -mm) is in
its most-synced-up state.

otoh, we should work out what our processes will be for keeping ext3 and
ext4 in sync wrt bugfixes, cleanups, speedups, etc. If those processes are
good, we can do the copy-n-paste any time. And they need to be good...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-08-10 19:07    [W:0.049 / U:12.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site