From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2013, #04; Fri, 12)
Date: Fri, 12 Apr 2013 15:56:06 -0700 [thread overview]
Message-ID: <7vr4ifbbp5.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <51688AF8.3010200@gmail.com> ("Jakub Narębski"'s message of "Sat, 13 Apr 2013 00:30:16 +0200")
Jakub Narębski <jnareb@gmail.com> writes:
> So mc/count-objects-kibibytes is to be discarded, or merged to 'master'?
I asked for opinions, not questions ;-)
I am on the fence, but slightly in favor of dropping it.
I suspect some scripts will get unexpectedly hurt, just like we had
to patch cvsimport. Among the human users who deeply care about the
output between "kilobytes" and "KiB", nobody would want "684322 KiB"
the "kibibytes" topic would give; people who care will likely to use
"-H" to obtain "668.28 MiB" instead.
prev parent reply other threads:[~2013-04-12 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 21:40 What's cooking in git.git (Apr 2013, #04; Fri, 12) Junio C Hamano
2013-04-12 22:30 ` Jakub Narębski
2013-04-12 22:56 ` Junio C Hamano [this message]
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=7vr4ifbbp5.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).