From 652c6bc40b438ab448535ae1b2a28cf3ba634325 Mon Sep 17 00:00:00 2001
From: "Kyle J. McKay" <mackyle@gmail.com>
Date: Tue, 9 Jul 2013 02:57:03 -0700
Subject: [PATCH] gc.sh: make repack parameters explicit, skip max-pack-size

Older versions of git interact badly with repack --max-pack-size
in that if more than one pack needs to be created, the total
repository size will tend to balloon up an awful lot.  Having
just 4 pack files can result in a 2x repository size.

Avoid using --max-pack-size at all and make the other parameters
explicit to avoid variations from external config files.
---
 jobd/gc.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/jobd/gc.sh b/jobd/gc.sh
index 393b97c..920004d 100755
--- a/jobd/gc.sh
+++ b/jobd/gc.sh
@@ -51,7 +51,7 @@ if [ -d "../${forkdir##*/}" ]; then
 fi
 
 quiet=; [ -n "$show_progress" ] || quiet=-q
-git repack -a -d --window-memory=1G --max-pack-size=250M -l $quiet
+git repack -a -d --window=50 --window-memory=1G --depth=50 -l $quiet
 git prune
 git update-server-info
 config_set lastgc "$(date "$datefmt")"
-- 
2.11.4.GIT