Re: [PATCH] git-clone.txt: Adjust note to --shared for new pruning behavior of git-gc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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 (or, hopefully,
"never" or "false").

-- 
Jakub Narebski
Poland
ShadeHawk on #git
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux