From: Mikael Magnusson <mikachu@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH] Correct output of git-count-objects.
Date: Mon, 8 Sep 2008 19:56:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.1.00.0809081952590.30512@localhost> (raw)
The non-verbose output was not changed in
fdb2a2a600969598fd80f01b009fbbb020d596ab ("compat: introduce on_disk_bytes()")
which caused git-count-objects to claim 512 times too much space used for
loose objects.
---
builtin-count-objects.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/builtin-count-objects.c b/builtin-count-objects.c
index 6e80fe7..ab35b65 100644
--- a/builtin-count-objects.c
+++ b/builtin-count-objects.c
@@ -126,6 +126,6 @@ int cmd_count_objects(int argc, const char **argv, const char *prefix)
}
else
printf("%lu objects, %lu kilobytes\n",
- loose, loose_size / 2);
+ loose, loose_size / 1024);
return 0;
}
--
1.6.0.GIT
--
Mikael Magnusson
next reply other threads:[~2008-09-08 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 17:56 Mikael Magnusson [this message]
2008-09-08 23:00 ` [PATCH] Correct output of git-count-objects 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=alpine.LNX.1.00.0809081952590.30512@localhost \
--to=mikachu@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).