summaryrefslogtreecommitdiff
path: root/commit.c
diff options
context:
space:
mode:
authorJohannes Sixt <johannes.sixt@telecom.at>2008-04-14 10:51:33 +0200
committerShawn O. Pearce <spearce@spearce.org>2008-04-14 19:34:23 -0400
commitdd70f3dbe48b9e30589c5832e95229b474651d6a (patch)
tree55d9eedb58945259ef661850938c47cfe7915e58 /commit.c
parent729ffa50f75a025935623bfc58d0932c65f7de2f (diff)
downloadgit-dd70f3dbe48b9e30589c5832e95229b474651d6a.tar.gz
git-gui: Report less precise object estimates for database compression
On startup, git-gui warns if there are many loose objects. It does so by saying, e.g., that there are "approximately 768 loose objects". But isn't "768" a very accurate number? Lets say "750", which (while still being a very precise number) sounds much more like an estimation. Signed-off-by: Johannes Sixt <johannes.sixt@telecom.at> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions