From: Eric Sandeen <esandeen@redhat.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] mke2fs, tune2fs, resize2fs: add warning messages for bigalloc and quota
Date: Tue, 22 Jan 2013 11:46:26 -0600 [thread overview]
Message-ID: <50FED072.2020402@redhat.com> (raw)
In-Reply-To: <355F6D97-0481-45C8-805B-F2E2BF6118F8@dilger.ca>
On 1/22/13 11:24 AM, Andreas Dilger wrote:
> My preference would be to have separate "--force-bigalloc" and
> "--force-quota" options instead of lumping everything under a single
> "--force/-f" flag. That can become habitual for one kind of usage
> (e.g. mke2fs on a regular file) and then it also forces other
> dangerous behaviour (such as these) as an unknown side effect.
Actually, that's a good point, I had the same thought and meant
to mention it but forgot. :(
I guess the release is out there now, though.
-Eric
next prev parent reply other threads:[~2013-01-22 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 0:09 [PATCH] mke2fs, tune2fs, resize2fs: add warning messages for bigalloc and quota Theodore Ts'o
2013-01-22 0:19 ` Eric Sandeen
2013-01-22 17:24 ` Andreas Dilger
2013-01-22 17:46 ` Eric Sandeen [this message]
2013-01-22 18:45 ` Theodore Ts'o
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=50FED072.2020402@redhat.com \
--to=esandeen@redhat.com \
--cc=adilger@dilger.ca \
--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 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).