From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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: Sat, 03 Nov 2007 16:30:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.9999.0711031627000.21255@xanadu.home> (raw)
In-Reply-To: <alpine.LFD.0.999.0711031229470.15101@woody.linux-foundation.org>
On Sat, 3 Nov 2007, Linus Torvalds wrote:
>
>
> On Sat, 3 Nov 2007, Nicolas Pitre wrote:
> >
> > Receiving objects: 100% (5439/5439), 1.60 MiB | 636 KiB/s, done.
>
> I mostly like this, but can we please just use "MB/kB" instead of
> "MiB/KiB"?
>
> I hope it was some kind of joke on crazy EU bureaucrats that just wasn't
> caught in time.
I don't care either ways. In fact my own preference is for MB/kB, but
if I had used that first I'm sure someone else would have asked for the
purist notations.
Nicolas
next prev parent reply other threads:[~2007-11-03 20:30 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 [this message]
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
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=alpine.LFD.0.9999.0711031627000.21255@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).