diff options
| author | Johannes Sixt <johannes.sixt@telecom.at> | 2008-04-14 08:51:33 (GMT) |
|---|---|---|
| committer | Shawn O. Pearce <spearce@spearce.org> | 2008-04-14 23:34:23 (GMT) |
| commit | dd70f3dbe48b9e30589c5832e95229b474651d6a (patch) | |
| tree | 55d9eedb58945259ef661850938c47cfe7915e58 /lib/database.tcl | |
| parent | 729ffa50f75a025935623bfc58d0932c65f7de2f (diff) | |
| download | git-dd70f3dbe48b9e30589c5832e95229b474651d6a.zip git-dd70f3dbe48b9e30589c5832e95229b474651d6a.tar.gz git-dd70f3dbe48b9e30589c5832e95229b474651d6a.tar.bz2 | |
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 'lib/database.tcl')
| -rw-r--r-- | lib/database.tcl | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/database.tcl b/lib/database.tcl index d66aa3f..a18ac8b 100644 --- a/lib/database.tcl +++ b/lib/database.tcl @@ -102,8 +102,8 @@ proc hint_gc {} { *]] if {$objects_current >= $object_limit} { - set objects_current [expr {$objects_current * 256}] - set object_limit [expr {$object_limit * 256}] + set objects_current [expr {$objects_current * 250}] + set object_limit [expr {$object_limit * 250}] if {[ask_popup \ [mc "This repository currently has approximately %i loose objects. |