From: Chris Frost <chris@frostnet.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] mke2fs.8.in: correct the sign of a block-size constraint.
Date: Wed, 28 Jul 2010 21:11:09 -0700 [thread overview]
Message-ID: <20100729041108.GA6251@pooh.frostnet.net> (raw)
In-Reply-To: <4C4BC3DB.5000008@redhat.com>
On Sat, Jul 24, 2010 at 11:55:55PM -0500, Eric Sandeen wrote:
> wow I didn't even know that behavior existed.
>
> How about "If block-size is preceded by a negative sign ("-"), then mke2fs
> will use heuristics to determine the appropriate block size, with the
> constraint that the block size will be at least block-size bytes."
I think this is more readable; thanks!
--
Chris Frost
http://www.frostnet.net/chris/
next prev parent reply other threads:[~2010-07-29 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 22:01 [PATCH] mke2fs.8.in: correct the sign of a block-size constraint Chris Frost
2010-07-25 4:55 ` Eric Sandeen
2010-07-29 4:11 ` Chris Frost [this message]
2010-07-29 16:59 ` [PATCH V2] mke2fs.8.in: clarify " Eric Sandeen
2010-07-31 0:40 ` Ted 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=20100729041108.GA6251@pooh.frostnet.net \
--to=chris@frostnet.net \
--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).