On Tue, Nov 3, 2015 at 1:44 PM, Andreas Krey <a.krey@xxxxxx> wrote: > Hi all, > > I have a bit of an annoying behaviour in git gc; > there is a repo I regularly do a fetch in, and > this kicks off a gc/prune every time. I remember > there being a heuristic with being that many files > in .git/objects/17 as the gc trigger. > > Which is unfortunate if the gc does not actually > reduce the number of files there because they > aren't old enough => gc comes right back. > > What can I do there? (This git is a bit old, 2.2.2) Run "git prune". 2.2.2 hides this suggestion to run git-prune in this case. The next git version will show it back. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html