garbage collection should be off for git repositories

Viewing diff on pom.xml on 338f39b changeset yields error, just click the diff icon on https://atlaseye.atlassian.com/changelog/stash?cs=338f39b7b16439da3974481872f5b5189d3bb3a6
It seems like this changeset is no longer in the history of https://stash.dev.internal.atlassian.com/projects/STASH/repos/stash/commits project, so I'm guessing this branch was abandoned or rebased to other changesets.
This changeset is no longer in local clone on atlaseye, I'm guessing it was purged by gc automatically, note this change is 30 days old at the moment (git default prune period seems to be 2 weeks, see http://git-scm.com/docs/git-gc)

Please validate the gc is indeed causing such orphaned changesets to be removed from local clone. Consider then changing local clone configuration by default to disable pruning of unreferenced objects completely. Perhaps objects should only be pruned on full reindex, otherwise as long as the changesets live in infinityDB and Lucene indexes we clearly want to keep them in in the local clone.