On Tue, Mar 19 2019, Johannes Sixt wrote: > Am 18.03.19 um 17:15 schrieb Ævar Arnfjörð Bjarmason: >> +Using this option may optimize for disk space at the expense of >> +runtime performance. See the `--depth` and `--window` documentation in >> +linkgit:git-repack[1]. It is not recommended that this option be used >> +to improve performance for a given repository without running tailored >> +performance benchmarks on it. It may make things better, or worse. Not >> +using this at all is the right trade-off for most users and their >> +repositories. >> ++ >> +The effects of this option are persistent to the extent that >> +`gc.autoPackLimit` and friends don't cause a consolidation of existing >> +pack(s) generated with this option. > > The first paragraph talks about potential downsides. And I think that > the second paragraph attempts to tell me how I can back out if I'm hit > by those downsides. But I have not the slightest idea how to read this > sentence and know what I have to do. That's an existing issue, but I'm fine with improving the docs even more, will add that :) You need to repack non-aggressively with the -f option. Right now there's nothing that exposes that from "gc", except setting the "aggressive" settings to the same as the default window/depth.
