All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, tytso@MIT.EDU, adilger@dilger.ca
Subject: Re: [PATCH v2 2/2] mke2fs: use binary units in the man page
Date: Thu, 19 May 2011 15:33:44 -0500	[thread overview]
Message-ID: <4DD57EA8.5040506@redhat.com> (raw)
In-Reply-To: <1297256607-4654-2-git-send-email-lczerner@redhat.com>

On 2/9/11 7:03 AM, Lukas Czerner wrote:
> (v2: do not spell units - mebibytes etc... - but rather use just abbrev.)
> 
> Decimal units (kilobyte 10^3, megabyte 10^6 etc...) were used in
> mke2fs manual page, however they was really meant to be binary units
> (kibibyte 2^10, mebibyte 2^20 etc...), so change the man pages to
> reflect that fact, even if it sounds weird.
> 
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>

Specificity is good, IMHO.

Reviewed-by: Eric Sandeen <sandeen@redhat.com>


> ---
>  misc/mke2fs.8.in |   14 +++++++-------
>  1 files changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in
> index e093be0..7933dca 100644
> --- a/misc/mke2fs.8.in
> +++ b/misc/mke2fs.8.in
> @@ -354,9 +354,9 @@ The following journal options are supported:
>  .BI size= journal-size
>  Create an internal journal (i.e., stored inside the filesystem) of size
>  .I journal-size
> -megabytes.
> +MiB.
>  The size of the journal must be at least 1024 filesystem blocks
> -(i.e., 1MB if using 1k blocks, 4MB if using 4k blocks, etc.)
> +(i.e., 1MiB if using 1024 byte blocks, 4MiB if using 4096 byte blocks, etc.)
>  and may be no more than 102,400 filesystem blocks.
>  @JDEV@.TP
>  @JDEV@.BI device= external-journal
> @@ -633,21 +633,21 @@ using a comma separated list.
>  If this option is is not specified,
>  .B mke2fs
>  will pick a single default usage type based on the size of the filesystem to
> -be created.  If the filesystem size is less than or equal to 3 megabytes,
> +be created.  If the filesystem size is less than or equal to 3 MiB,
>  .B mke2fs
>  will use the filesystem type
>  .IR floppy .
>  If the filesystem size is greater than 3 but less than or equal to
> -512 megabytes,
> +512 MiB,
>  .BR mke2fs (8)
>  will use the filesystem type
>  .IR small .
> -If the filesystem size is greater than or equal to 4 terabytes but less than
> -16 terabytes,
> +If the filesystem size is greater than or equal to 4 TiB but less than
> +16 TiB,
>  .BR mke2fs (8)
>  will use the filesystem type
>  .IR big .
> -If the filesystem size is greater than or equal to 16 terabytes,
> +If the filesystem size is greater than or equal to 16 TiB,
>  .BR mke2fs (8)
>  will use the filesystem type
>  .IR huge .


  reply	other threads:[~2011-05-19 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 13:03 [PATCH v2 1/2] e2fsprogs: Fix how we treat user-spcified filesystem size Lukas Czerner
2011-02-09 13:03 ` [PATCH v2 2/2] mke2fs: use binary units in the man page Lukas Czerner
2011-05-19 20:33   ` Eric Sandeen [this message]
2011-05-16 13:49 ` [PATCH v2 1/2] e2fsprogs: Fix how we treat user-spcified filesystem size Lukas Czerner
2011-05-19 20:32 ` Eric Sandeen
2011-05-20  9:07   ` Lukas Czerner
2011-05-20 12:22     ` Lukas Czerner

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=4DD57EA8.5040506@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@dilger.ca \
    --cc=lczerner@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.