All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: tytso@mit.edu
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: what exactly is CONFIG_EXT4_USE_FOR_EXT23 for?
Date: Thu, 11 Mar 2010 14:44:25 -0600	[thread overview]
Message-ID: <4B995629.6020402@redhat.com> (raw)
In-Reply-To: <20100311204020.GK1497@thunk.org>

tytso@mit.edu wrote:
> On Thu, Mar 11, 2010 at 01:54:42PM -0600, Eric Sandeen wrote:
>> As long as it doesn't contaminate the "core" then sure, but the more twisty
>> paths we have, the less likely any of them will be maintainable.  :)
>>
>> I just think that before adding more knobs, we need to take a long hard
>> look at what it does to the big picture.  When documenting ext4 upstream,
>> how many "if ... else if ... else if" clauses do we need?
> 
> Fair enough.
> 
> I'm all for proposals to get rid of some knobs, too, if we don't think
> they serve a purpose.  Recent examples that we've started deprecated
> include minixdf --- and I really wonder if we need t have explicit
> mount options to enable xattr and acl's.  Anyone object if we just
> enable them all the time by default?
> 
>               	    	    	    - Ted

I'd be happy with that.  It always bites me when I forget ;)

Do we still need auto_da_alloc as a disable-able option?

-Eric

      reply	other threads:[~2010-03-11 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 16:38 what exactly is CONFIG_EXT4_USE_FOR_EXT23 for? Eric Sandeen
2010-03-11 17:27 ` Jan Kara
2010-03-11 20:37   ` tytso
2010-03-11 19:40 ` tytso
2010-03-11 19:54   ` Eric Sandeen
2010-03-11 20:40     ` tytso
2010-03-11 20:44       ` Eric Sandeen [this message]

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=4B995629.6020402@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.