git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Hommey <mh@glandium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Nicolas Pitre <nico@cam.org>, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH] git-fetch: more terse fetch output
Date: Sun, 4 Nov 2007 00:54:55 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711040050430.4362@racer.site> (raw)
In-Reply-To: <20071103233144.GA16734@glandium.org>

Hi,

On Sun, 4 Nov 2007, Mike Hommey wrote:

> On Sat, Nov 03, 2007 at 03:48:42PM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Sat, 3 Nov 2007, Mike Hommey wrote:
> > > 
> > > How many grams in a kilogram ? How many meters in a kilometer ? How many
> > > joule in a kilojoule ? ... How many bytes in a kilobyte ? Oh wait...
> > 
> > How many 'u's in the word "colour"?
> > 
> > Oh, wait - it depends on context, doesn't it?
> > 
> > kB is 1024 bytes. The fact that "k" means something else in other 
> > contexts is simply irrelevant.
> 
> What about the fact that "kB" means different things depending whether 
> it's used for bandwidth or memory capacity ?
>
> Does your brain have base 2 hard-coded so that you instantly know 
> 50000000 bytes are 47.68MB ? Are people unable to do so pondscum ?

Get over it.  kB is not the same as km.  It really means something 
different.  And all all people who actually _understand_ something of the 
matter know what a kilobyte is.

Just because some _wankers_^Wbureaucrats decided to make life hard on 
those people who have actually a _clue_ on real life, does not mean that 
we have to accept it.

1kB = 1024 bytes.

1MB = 1024*1024 bytes.

Everybody who claims anything else is just an annoyance to the rest of the 
world, who is not clueless, thank you very much.

And hard disk manufacturers be damned, and should burn in hell.

Ciao,
Dscho

  reply	other threads:[~2007-11-04  0:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03  5:32 [PATCH] git-fetch: more terse fetch output Nicolas Pitre
2007-11-03  5:36 ` Junio C Hamano
2007-11-03 19:34 ` Linus Torvalds
2007-11-03 20:30   ` Nicolas Pitre
2007-11-03 20:40     ` Mike Hommey
2007-11-03 20:50       ` Nicolas Pitre
2007-11-03 21:03         ` Mike Hommey
2007-11-03 21:46           ` Pierre Habouzit
2007-11-03 22:02           ` Jakub Narebski
2007-11-03 22:48           ` Linus Torvalds
2007-11-03 23:31             ` Mike Hommey
2007-11-04  0:54               ` Johannes Schindelin [this message]
2007-11-04  1:03                 ` Junio C Hamano
2007-11-04  1:49                   ` David Brown
2007-11-04  2:14                     ` Robin Rosenberg
2007-11-03 22:45         ` Linus Torvalds
2007-11-04  9:56         ` Steffen Prohaska
2007-11-04  4:58 ` Jeff King
2007-11-04 13:13   ` Johannes Schindelin
2007-11-04 14:01     ` Pierre Habouzit

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=Pine.LNX.4.64.0711040050430.4362@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mh@glandium.org \
    --cc=nico@cam.org \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    --cc=torvalds@linux-foundation.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 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).