What happens when the repository is bigger than gc.autopacklimit * pack.packSizeLimit?

2014-08-27 Thread Dale R. Worley
[Previously sent to the git-users mailing list, but it probably should be addressed here.] A number of commands invoke git gc --auto to clean up the repository when there might be a lot of dangling objects and/or there might be far too many unpacked files. The manual pages say: git gc:

Re: What happens when the repository is bigger than gc.autopacklimit * pack.packSizeLimit?

2014-08-27 Thread Jeff King
On Wed, Aug 27, 2014 at 03:36:53PM -0400, Dale R. Worley wrote: And it appears from an experiment that this is what happens. I have a repository with pack.packSizeLimit = 99m, and there are 104 pack files, and even when git gc is done, if I do git gc --auto, it will do git-repack again. I

Re: What happens when the repository is bigger than gc.autopacklimit * pack.packSizeLimit?

2014-08-27 Thread Junio C Hamano
wor...@alum.mit.edu (Dale R. Worley) writes: builtin/gc.c: static int too_many_packs(void) { struct packed_git *p; int cnt; if (gc_auto_pack_limit = 0) return 0; prepare_packed_git(); for (cnt = 0, p = packed_git; p; p = p-next) {