| commit | dd70f3dbe48b9e30589c5832e95229b474651d6a | |
| author | Johannes Sixt <johannes.sixt@telecom.at> | |
| Mon, 14 Apr 2008 08:51:33 +0000 (14 10:51 +0200) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 14 Apr 2008 23:34:23 +0000 (14 19:34 -0400) | ||
| tree | 55d9eedb58945259ef661850938c47cfe7915e58 | treesnapshot (tar.gz zip) |
| parent | 729ffa50f75a025935623bfc58d0932c65f7de2f | commitdiff |
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>
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>
| lib/database.tcl | diffblobblamehistory |