From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: Re: [PATCH 2/3] differentiate between S.I. and binary units in output
Date: Mon, 28 Sep 2009 09:17:59 -0400 [thread overview]
Message-ID: <20090928131758.GA26763@redhat.com> (raw)
In-Reply-To: <20090928124906.GD5351@agk-dp.fab.redhat.com>
On Mon, Sep 28 2009 at 8:49am -0400,
Alasdair G Kergon <agk@redhat.com> wrote:
> On Sat, Sep 26, 2009 at 05:33:46PM +0200, Daniel Mierswa wrote:
> > For binary based uints:
> > Long output strings (unsed) will be Kibibyte, Mebibyte, etc.
> > Short output strings will be KiB, MiB, etc.
> > Unit output strings will be lower-cased: k, m, g, etc.
> > Sectors determined by division with 512 will be suffixed with s.
> > For S.I. based units:
> > Long output strings (unused) will be Kilobyte, Megabyte, etc.
> > Short output strings will be kB, MB, GB, etc.
> > Unit output strings will be upper-cased: K, M, G, etc.
> > Sectors determined by division with 500 will be suffixed with S.
>
> Bytes, Units and Sectors are special cases - in a separate group.
> A sector is always 512 bytes. I don't see any need to support 500-byte
> sectors.
I agree that 500-byte sectors aren't meaningful but I added support for
them a few months ago to be consistent, see:
http://sources.redhat.com/git/?p=lvm2.git;a=commit;h=69da2ac0
next prev parent reply other threads:[~2009-09-28 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 15:33 [PATCH 1/3] use display_size function instead of hardcoding Daniel Mierswa
2009-09-26 15:33 ` [PATCH 2/3] differentiate between S.I. and binary units in output Daniel Mierswa
2009-09-28 12:49 ` Alasdair G Kergon
2009-09-28 13:17 ` Mike Snitzer [this message]
2009-09-28 14:25 ` Alasdair G Kergon
2009-09-28 14:37 ` Mike Snitzer
2009-09-28 16:44 ` Alasdair G Kergon
2009-09-30 1:00 ` Daniel Mierswa
2009-09-30 14:20 ` Alasdair G Kergon
2009-09-26 15:33 ` [PATCH 3/3] adjust the testsuite to work with new output Daniel Mierswa
2009-09-28 12:15 ` [PATCH 1/3] use display_size function instead of hardcoding Alasdair G Kergon
2009-09-28 16:31 ` Alasdair G Kergon
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=20090928131758.GA26763@redhat.com \
--to=snitzer@redhat.com \
--cc=lvm-devel@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 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.