Re: [gpsd-dev] Please "git gc --aggressive" the gpsd repository?

[Greg Troxel]

Thanks for the link - that helps a lot.

So I conclude:

  "gc --aggressive" is misnamed, because it results in the same set of
  reachable objects, and aggressiveness in gc doesn't make sense anyway

  --aggressive does result in different compresssion, often better if
  the old compression was bad

  there's nothing scary about it in terms of data integrity


I tried this on a few repos of mine (which were not the result of
import/etc. - native git the whole time).  git gc cleaned up a lot,
mostly from coalescing loose objects.   And --aggressive reduced 1300K
to 1040K more or less, as a typical case.  The repack with depth=250 did
exactly the same as gc --aggressive.

So while the caution about --aggressive may be generally true, if one
clones a repo and a gc --aggressive drops the space usage a lot, that
probably means it's a good idea upstream.

pgpU1ePR2Ilum.pgp
Description: PGP signature