From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jan Smets <jan.smets@alcatel-lucent.com>, <git@vger.kernel.org>
Subject: Re: repository corruption when pushing commits to a repository running 'git gc --prune='
Date: Wed, 14 Oct 2015 20:40:02 +0200 [thread overview]
Message-ID: <vpqmvvl8fb1.fsf@grenoble-inp.fr> (raw)
In-Reply-To: <xmqqoag18i6w.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 14 Oct 2015 10:37:43 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> 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/
next prev parent reply other threads:[~2015-10-14 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 13:44 repository corruption when pushing commits to a repository running 'git gc --prune=' Jan Smets
2015-10-14 14:38 ` Matthieu Moy
2015-10-14 17:37 ` Junio C Hamano
2015-10-14 18:40 ` Matthieu Moy [this message]
2015-10-14 20:48 ` Junio C Hamano
2015-10-14 21:09 ` Matthieu Moy
2015-10-14 21:39 ` Junio C Hamano
2015-10-14 18:46 ` Matthieu Moy
2015-10-14 20:05 ` Junio C Hamano
2015-10-14 20:08 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqmvvl8fb1.fsf@grenoble-inp.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jan.smets@alcatel-lucent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).