From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [E2FSPROGS, RFC] New mke2fs types parsing
Date: Wed, 20 Feb 2008 12:51:21 -0600 [thread overview]
Message-ID: <47BC76A9.307@redhat.com> (raw)
In-Reply-To: <E1JRpaN-0000Bs-4N@closure.thunk.org>
Theodore Ts'o wrote:
> The following patch is a work in progress, but I'm sending it out so
> folks can take a look at it and comment on the general approach.
>
> What this does is change how mke2fs -T works so it can take a comma
> separated list, so you can do things like this:
>
> mke2fs -T ext4,small,news
Is there some hierarchy of what these options are and how they fit
together? i.e. small & news might go together (in bizarro world...) but
"small,large" wouldn't make sense - nor would -T ext3,ext4. Or, if
somebody stores mail & news on the same fs, nad they say -T mail,news
but the mail & news types have conflicting directives...
how will you define what an acceptable composite of subtypes will be?
Thanks,
-Eric
next prev parent reply other threads:[~2008-02-20 18:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 14:06 [E2FSPROGS, RFC] New mke2fs types parsing Theodore Ts'o
2008-02-20 18:51 ` Eric Sandeen [this message]
2008-02-20 22:20 ` Theodore Tso
2008-02-20 22:28 ` Eric Sandeen
2008-02-21 8:52 ` Andreas Dilger
2008-02-21 13:35 ` Theodore Tso
2008-03-17 21:29 ` Eric Sandeen
2008-03-18 2:20 ` Theodore Tso
2008-03-18 3:23 ` Eric Sandeen
2008-03-18 4:23 ` Theodore Tso
2008-03-18 5:16 ` Eric Sandeen
2008-03-18 11:01 ` Theodore Tso
2008-03-18 13:11 ` Eric Sandeen
2008-03-18 13:52 ` Theodore Tso
2008-03-18 16:06 ` Eric Sandeen
2008-03-20 19:17 ` Eric Sandeen
2008-03-20 20:49 ` Theodore Tso
2008-03-19 3:36 ` Andreas Dilger
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=47BC76A9.307@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.