public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@phunq.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	tux3@tux3.org
Subject: Re: Tux3 report: Tux3 by Christmas?
Date: Thu, 11 Dec 2008 00:59:24 -0800	[thread overview]
Message-ID: <200812110059.25155.phillips@phunq.net> (raw)
In-Reply-To: <20081210233617.ddb3fa30.akpm@linux-foundation.org>

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

Regards,

Daniel

  reply	other threads:[~2008-12-11  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 22:35 Tux3 report: Tux3 by Christmas? Daniel Phillips
2008-12-11  2:29 ` [Tux3] " Daniel Phillips
2008-12-11  7:36 ` Andrew Morton
2008-12-11  8:59   ` Daniel Phillips [this message]
2008-12-11 14:58   ` John Stoffel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200812110059.25155.phillips@phunq.net \
    --to=phillips@phunq.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tux3@tux3.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox