From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2 Date: Thu, 10 Aug 2006 01:58:57 -0400 Message-ID: <44DACB21.9080002@garzik.org> References: <1155172597.3161.72.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:15568 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S1161046AbWHJF7J (ORCPT ); Thu, 10 Aug 2006 01:59:09 -0400 To: cmm@us.ibm.com In-Reply-To: <1155172597.3161.72.camel@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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