Re: repository corruption when pushing commits to a repository running 'git gc --prune='
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Oct 14, 2015, 18:40 UTC
- Message-ID
- <vpqmvvl8fb1.fsf@grenoble-inp.fr>
- In-Reply-To
- <xmqqoag18i6w.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 15 quoted lines
> 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/