From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: Tux3 report: Tux3 by Christmas? Date: Wed, 10 Dec 2008 23:36:17 -0800 Message-ID: <20081210233617.ddb3fa30.akpm@linux-foundation.org> References: <200812101435.40393.phillips@phunq.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, tux3@tux3.org To: Daniel Phillips Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:37866 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754247AbYLKHg6 (ORCPT ); Thu, 11 Dec 2008 02:36:58 -0500 In-Reply-To: <200812101435.40393.phillips@phunq.net> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 10 Dec 2008 14:35:39 -0800 Daniel Phillips wrote: > The big goals for Christmas (this Christmas!) are: > > - SMP locking > - Atomic commit > - Posixly complete > - Rudimentary fsck > > ... > > Non-goals for Christmas include: > > - Versioning > - Directory indexing (PHTree) > - fsck repair If it is your intention to submit this for a mainline merge then I would encourage you to stop feature work at the earliest reasonable stage and then move into the document, submit, review, merge, fixfixfix phase. That might take as long as several months. Once things have stabilised and it's usable and performs respectably, start thinking about features again. Do NOT fall into the trap of adding more and more and more stuff to an out-of-tree project. It just makes it harder and harder to get it merged. There are many examples of this. Also, don't feel that a merge would lock you into the current on-disk layout. I think it would be acceptable to emit a big printk("the format of this fs will change without notice. Do not yet store any data on a tux3 fs") during mount(). For a while.