Re: People unaware of the importance of "git gc"?
From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:43:33
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: People unaware of the importance of "git gc"? · Linus Torvalds <torvalds@linux-foundation.org>
- 2016-06-15 · Re: People unaware of the importance of "git gc"? · Steven Grimm <hidden>
- 2016-06-15 · Re: People unaware of the importance of "git gc"? · Shawn O. Pearce <hidden>
- 2016-06-15 · Re: People unaware of the importance of "git gc"? · Johannes Schindelin <hidden>
- 2016-06-15 · People unaware of the importance of "git gc"? · Linus Torvalds <torvalds@linux-foundation.org>
Hi, On Wed, 5 Sep 2007, Junio C Hamano wrote:
quoted hunk ↗ jump to hunk
@@ -20,6 +20,7 @@ static const char builtin_gc_usage[] = "git-gc [--prune] [--aggressive]"; static int pack_refs = 1; static int aggressive_window = -1; +static int gc_auto_threshold = 6700;
Please don't do that. When you share objects with another git directory, git-gc --auto can get rid of the objects when some objects go away in the referenced repository. So we need _at least_ check gc.auto not being set in the repo when "git clone --share"ing it (and fail otherwise). My preferred way would be to set it in "git init" so that existing setups are not affected, and put some big red message on top of the next release notes that people might want to set gc.auto in their existing setups. Ciao, Dscho