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 15:01:20 -0400 Message-ID: <4489C580.7080001@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> <20060609181020.GB5964@schatzie.adilger.int> 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, Alex Tomas , Andreas Dilger Return-path: To: Chase Venters 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 Chase Venters wrote: > Now, granted, I really do agree with you about the whole code sharing > thing. A fresh start is often just what you need. I'm just questioning > if it wouldn't be better to do this fresh start immediately after going > 48-bit, rather than before. That way, existing users that want that > extra umph can have it today. Then you continue to crap up the code with if (48bit) ... else ... etc. The proper way to do this is "cp -a ext3 ext4" (excluding JBD as Andrew mentioned), and then let evolution take its course. "Evolution" means the standard Linux developement -- patch the kernel, patch e4fsprogs, test, lather rinse repeat. The best development platform for new features is one that _works_, and keeps working. Jeff