All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mail@bernhard-voelker.de" <mail@bernhard-voelker.de>
To: Karel Zak <kzak@redhat.com>
Cc: Simon de Vlieger <simon@ikanobori.jp>,
	"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Subject: Re: [PATCH] hexdump: adjust -s and -n option in the man page [was: hexsyntax.c using strtol on the offset parameter]
Date: Mon, 26 Mar 2012 09:20:26 +0200 (CEST)	[thread overview]
Message-ID: <917665944.185472.1332746426227.JavaMail.open-xchange@email.1und1.de> (raw)
In-Reply-To: <20120323171936.GH2040@x2.net.home>

 Karel Zak wrote:
> > From: Bernhard Voelker <mail@bernhard-voelker.de>
> > Date: Thu, 22 Mar 2012 12:53:06 +0100
> > Subject: [PATCH] hexdump: adjust -s and -n option in the man page
>
> Good point, I have copied the text we already have in the losetup man
> page.
>
> +The \fIlength\fR and \fIoffset\fR arguments may be followed by binary
(2^N)
> +suffixes KiB, MiB, GiB, TiB, PiB and EiB (the "iB" is optional, e.g. "K"
has the
> +same meaning as "KiB") or decimal (10^N) suffixes KB, MB, GB, PB and EB.

Thanks.

I have derived my patch proposal from the info pages of coreutils, as there
has recently been a discussion about the clearest wording.
I don't think all users are aware what's the difference between
"binary (2^N) suffixes KiB" and "decimal (10^N) suffixes KB".

BTW: why omitting the Z and the Y suffix in the man page?

Have a nice day, Berny

  reply	other threads:[~2012-03-26  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 11:58 [PATCH] hexdump: adjust -s and -n option in the man page [was: hexsyntax.c using strtol on the offset parameter] Bernhard Voelker
2012-03-23 17:19 ` Karel Zak
2012-03-26  7:20   ` mail [this message]
2012-03-26  8:41     ` Karel Zak
2012-03-26  9:39   ` mail
2012-03-26  9:50     ` mail
2012-03-30 13:34       ` Karel Zak
2012-03-30 13:26     ` Karel Zak

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=917665944.185472.1332746426227.JavaMail.open-xchange@email.1und1.de \
    --to=mail@bernhard-voelker.de \
    --cc=kzak@redhat.com \
    --cc=simon@ikanobori.jp \
    --cc=util-linux@vger.kernel.org \
    /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.