[Tux3] Tux3 report: Tux3 by Christmas?

Daniel Phillips phillips at phunq.net
Thu Dec 11 00:59:24 PST 2008

On Wednesday 10 December 2008 23:36, Andrew Morton wrote:
> On Wed, 10 Dec 2008 14:35:39 -0800 Daniel Phillips <phillips at phunq.net> 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.

I think I was getting all geared up to be another example of that.  Ok,
"usable" to me means with atomic commit and SMP locking, and doesn't
immediately oops.  And put the versioning and directory index aside for
the moment, which is not a big question mark because we have done both
> 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.

Got it.



Tux3 mailing list
Tux3 at tux3.org

More information about the Tux3 mailing list