Re: [PATCH] git-clone.txt: Adjust note to --shared for new pruning behavior of git-gc
- From
Brandon Casey <casey@nrlssc.navy.mil>
- Date
- Apr 4, 2008, 14:25 UTC
- Message-ID
- <47F63A71.2010100@nrlssc.navy.mil>
- In-Reply-To
- <m3prt6t8sn.fsf@localhost.localdomain>
Jakub Narebski wrote:
Show 14 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > >> On Thu, 3 Apr 2008, Brandon Casey wrote: >>> But what I was really trying to point out in the documentation changes >>> was that now _other_ commands such as git-commit are also unsafe since >>> they call 'git-gc --auto' and could cause loose unreferenced objects to >>> be deleted. So it is not enough to just avoid calling git-gc when >>> dealing with a --shared repository. >> Right. Hmm. I missed that completely when I thought about prune >> --expire. > > I think that if you are using repository from which other repos borrow > objects via alternates, it is a good idea to turn off automatic > repacking with "git gc --auto" by setting gc.auto to 0
Either that or disable only the automatic pruning by setting gc.pruneexpire to never.
> (or, hopefully, "never" or "false").
I think those only work for dates and booleans respectively. gc.auto is parsed as an int.
-brandon