From: Daniel Mierswa <impulze@impulze.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] S.I. and consistent units
Date: Tue, 30 Jun 2009 17:47:58 +0200 [thread overview]
Message-ID: <4A4A33AE.2050608@impulze.org> (raw)
In-Reply-To: <20090630111832.GB20848@agk-dp.fab.redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1023 bytes --]
The functional changes are as follows:
- Users and programs currently checking the output of LVM have to
distinguish between either IEC or SI units. Currently LVM prints K, KB
and Kilobyte for SI and IEC units depending on what they passed in
--units. With the patch applied LVM prints K, KB and Kilobyte for SI
units and k, KiB and Kibibyte for IEC units.
- Users and programs currently passing LVM the uppercase size suffixes
are now telling LVM to treat that value as SI unit whereas now LVM
treats lower and uppercase suffixes as IEC (binary based unit).
Consider this as an improved version of my initial patch with the fixes
you wanted applied. Let's make another feedback session now. :-)
That's all I can think of now, I'm more than happy to investigate
further and react upon your requests and feedback.
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22
[-- Attachment #1.2: lvm-units.patch.gz --]
[-- Type: application/gzip, Size: 17407 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-30 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 15:10 [linux-lvm] S.I. and consistent units Daniel Mierswa
2009-06-28 22:39 ` Daniel Mierswa
2009-06-29 5:50 ` Luca Berra
2009-06-29 9:23 ` Daniel Mierswa
2009-06-30 11:18 ` Alasdair G Kergon
2009-06-30 12:05 ` Daniel Mierswa
2009-06-30 13:17 ` Alasdair G Kergon
2009-06-30 15:47 ` Daniel Mierswa [this message]
2009-06-30 11:46 ` Jim Meyering
2009-06-29 14:01 ` Clyde E. Kunkel
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=4A4A33AE.2050608@impulze.org \
--to=impulze@impulze.org \
--cc=linux-lvm@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).