Re: repository corruption when pushing commits to a repository running 'git gc --prune='
From: Matthieu Moy <hidden>
Date: 2016-06-15 23:06:52
Junio C Hamano [off-list ref] writes:
quoted hunk
diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt index 5223498..fa15104 100644 --- a/Documentation/git-gc.txt +++ b/Documentation/git-gc.txt@@ -63,8 +63,11 @@ automatic consolidation of packs. --prune=<date>:: Prune loose objects older than date (default is 2 weeks ago, overridable by the config variable `gc.pruneExpire`). - --prune=all prunes loose objects regardless of their age. - --prune is on by default. + --prune=all prunes loose objects regardless of their age (do + not use --prune=all unless you know exactly what you are doing. + Unless the repository is quiescent, you will lose newly created + objects that haven't been anchored with the refs and end up + corrupting your repository). --prune is on by default.
Looks good to me. I think the same should be added to git-prune.txt under --expire. -- Matthieu Moy http://www-verimag.imag.fr/~moy/