From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [RFC 0/13] extents and 48bit ext3 Date: Fri, 09 Jun 2006 12:55:09 -0400 Message-ID: <4489A7ED.8070007@garzik.org> References: <1149816055.4066.60.camel@dyn9047017069.beaverton.ibm.com> <4488E1A4.20305@garzik.org> <20060609083523.GQ5964@schatzie.adilger.int> <44898EE3.6080903@garzik.org> <448992EB.5070405@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , ext2-devel , linux-kernel@vger.kernel.org, Linus Torvalds , cmm@us.ibm.com, linux-fsdevel@vger.kernel.org, Andreas Dilger Return-path: To: Alex Tomas In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ext2-devel-bounces@lists.sourceforge.net Errors-To: ext2-devel-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org Alex Tomas wrote: > so, instead of taking one (quite-well-tested) part that solves one of > the biggest ext3 limitation, you propose to start a new project and > get something in a year (probably) ? > > I think about extents as a step-by-step way ... That is what the entirety of Linux development is -- step-by-step. It is OBVIOUS that it would take five minutes to start ext4. 1) clone a new tree 2) cp -a fs/ext3 fs/ext4 3) apply extent and 48bit patches 4) apply related e2fsprogs patches Then update ext4 step-by-step, using the normal Linux development process. Jeff