From: "Jakub Narębski" <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2013, #04; Fri, 12)
Date: Sat, 13 Apr 2013 00:30:16 +0200 [thread overview]
Message-ID: <51688AF8.3010200@gmail.com> (raw)
In-Reply-To: <7vehefctrf.fsf@alter.siamese.dyndns.org>
W dniu 12.04.2013 23:40, Junio C Hamano pisze:
> --------------------------------------------------
> [New Topics]
> * ap/strbuf-humanize (2013-04-10) 2 commits
> - count-objects: add -H option to humanize sizes
> - strbuf: create strbuf_humanise_bytes() to show byte sizes
>
> Teach "--human-readable" aka "-H" option to "git count-objects" to
> show various large numbers in Ki/Mi/GiB scaled as necessary.
>
> Will merge to 'next'.
>
> It may not be a bad idea to discard mc/count-objects-kibibytes,
> which can introduce regression to scripted users that expect the
> output to say "N kilobytes". Opinions?
> --------------------------------------------------
> [Cooking]
> * mc/count-objects-kibibytes (2013-04-03) 1 commit
> (merged to 'next' on 2013-04-05 at f4e50e8)
> + count-objects: output "KiB" instead of "kilobytes"
>
> The command reports the total diskspace used to store loose objects
> in kibibytes, but it was labelled as "kilobytes". The number now
> is shown with "KiB", e.g. "6750 objects, 50928 KiB".
>
> If you have scripts that decide when to run "git repack" by parsing
> the output from "git count-objects", this release may break them.
> Sorry about that. One of the scripts shipped by git-core itself
> also had to be adjusted. You may want to consider updating such
> scripts to always call "git gc --auto" to let it decide when to
> repack for you.
>
> Will merge to 'master'.
So mc/count-objects-kibibytes is to be discarded, or merged to 'master'?
--
Jakub Narębski
next prev parent reply other threads:[~2013-04-12 22:30 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 [this message]
2013-04-12 22:56 ` Junio C Hamano
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=51688AF8.3010200@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).