All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: cmm@us.ibm.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2
Date: Thu, 10 Aug 2006 01:58:57 -0400	[thread overview]
Message-ID: <44DACB21.9080002@garzik.org> (raw)
In-Reply-To: <1155172597.3161.72.camel@localhost.localdomain>

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.

	Jeff



  reply	other threads:[~2006-08-10  5:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:16 [PATCH 0/5] Forking ext4 filesystem and JBD2 Mingming Cao
2006-08-10  5:58 ` Jeff Garzik [this message]
2006-08-10 16:33   ` Mingming Cao
2006-08-10 17:00     ` Andrew Morton
2006-08-10 17:00       ` Andrew Morton
2006-08-14 21:44       ` Pavel Machek
2006-08-15 19:06         ` Jeff Garzik
2006-08-10 14:02 ` Michal Piotrowski
2006-08-10 15:15   ` Michal Piotrowski
2006-08-10 15:15     ` Michal Piotrowski
2006-08-10 19:06     ` John McCutchan
2006-08-10 19:06       ` John McCutchan
2006-08-10 19:06       ` John McCutchan
2006-08-19 18:42     ` John McCutchan
2006-08-19 18:42       ` John McCutchan
2006-08-19 18:42       ` John McCutchan
2006-08-19 21:17         ` Michal Piotrowski
2006-08-19 21:17           ` Michal Piotrowski

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=44DACB21.9080002@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.