LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Heikki Orsila <shdl@zakalwe.fi>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Tony Foiani <tkil@scrye.com>,
Leon Woestenberg <leon.woestenberg@gmail.com>,
linux-kernel@vger.kernel.org,
David Schwartz <davids@webmaster.com>
Subject: Re: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)
Date: Sun, 21 Jan 2007 17:06:18 +0200 [thread overview]
Message-ID: <20070121150618.GA11613@zakalwe.fi> (raw)
In-Reply-To: <E1H8a7s-0000at-Jx@be1.lrz>
On Sun, Jan 21, 2007 at 11:40:40AM +0100, Bodo Eggert wrote:
> 1) This change isn't nescensary - any sane person will know that it's not a
> SI unit. You wouldn't talk about megabananas == 1000000 bananas and
> expect to be taken seriously.
I've met quite a few non-sane persons then. I find using kilo, mega and
giga prefixes convenient to use. For example, I often use GEUR to refer
to Giga Euros, because the word billion is overloaded.
> 2) No sane person would say kibibyte as required by the standard. You'd need
> a sppech defect in order to do this, and a mental defect in order to try.
> So why should anybody adhere to the rest of this bullshit?
I think I'm not sane then. I find it easy to use and pronounce.
IEC 60027-2 is a great standard! It removes some annoying ambiquity in
speech and text. Adhering strictly to proper SI units (k, M, G, ...)
makes life easier as they are taught in school to everyone.
--
Heikki Orsila Barbie's law:
heikki.orsila@iki.fi "Math is hard, let's go shopping!"
http://www.iki.fi/shd
next prev parent reply other threads:[~2007-01-21 15:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7FsPf-51s-9@gated-at.bofh.it>
[not found] ` <7FxlV-3sb-1@gated-at.bofh.it>
[not found] ` <7FyUF-5XD-21@gated-at.bofh.it>
2007-01-21 10:40 ` Bodo Eggert
2007-01-21 11:10 ` Eduard Bloch
2007-01-21 22:08 ` Stefan Richter
2007-01-22 15:53 ` Lennart Sorensen
2007-01-22 16:58 ` Jan Engelhardt
2007-01-22 18:36 ` Alan
2007-01-22 19:24 ` Tony Foiani
2007-01-22 22:26 ` Bodo Eggert
2007-01-22 20:44 ` Lennart Sorensen
2007-01-22 21:17 ` linux-os (Dick Johnson)
2007-01-22 20:43 ` Lennart Sorensen
2007-01-22 21:22 ` Jan Engelhardt
2007-01-21 14:45 ` Benny Amorsen
2007-01-21 15:06 ` Heikki Orsila [this message]
2007-01-21 21:27 ` Jan Engelhardt
2007-01-22 1:56 ` Krzysztof Halasa
2007-01-22 10:39 ` Bernd Petrovitsch
2007-01-22 10:48 ` Andreas Schwab
2007-01-23 1:04 ` Krzysztof Halasa
2007-01-23 1:45 ` Jan Engelhardt
2007-01-23 9:23 ` Andreas Schwab
2007-01-23 13:14 ` Krzysztof Halasa
2007-01-20 8:08 Michał Kudła
2007-01-20 10:29 ` David Schwartz
2007-01-20 18:07 ` Leon Woestenberg
2007-01-20 22:54 ` David Schwartz
2007-01-21 0:07 ` Tony Foiani
2007-01-21 21:12 ` Jan Engelhardt
2007-01-22 6:45 ` Tony Foiani
2007-01-22 8:25 ` Roland Kuhn
2007-01-22 15:43 ` Lennart Sorensen
2007-01-21 7:11 ` H. Peter Anvin
2007-01-21 20:03 ` Geert Uytterhoeven
2007-01-21 20:06 ` H. Peter Anvin
2007-01-21 17:04 ` Leon Woestenberg
2007-01-21 22:12 ` David Schwartz
2007-01-22 8:49 ` Benny Amorsen
2007-01-27 15:06 ` Andries Brouwer
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=20070121150618.GA11613@zakalwe.fi \
--to=shdl@zakalwe.fi \
--cc=7eggert@gmx.de \
--cc=davids@webmaster.com \
--cc=leon.woestenberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tkil@scrye.com \
--subject='Re: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)' \
/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
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).