From: tytso@mit.edu
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: what exactly is CONFIG_EXT4_USE_FOR_EXT23 for?
Date: Thu, 11 Mar 2010 15:40:20 -0500 [thread overview]
Message-ID: <20100311204020.GK1497@thunk.org> (raw)
In-Reply-To: <4B994A82.8010204@redhat.com>
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
next prev parent reply other threads:[~2010-03-11 20:40 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 [this message]
2010-03-11 20:44 ` Eric Sandeen
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=20100311204020.GK1497@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).