From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-clone.txt: Adjust note to --shared for new pruning behavior of git-gc
Date: Thu, 03 Apr 2008 23:49:10 -0700 (PDT) [thread overview]
Message-ID: <m3prt6t8sn.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LSU.1.00.0804032200310.4008@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> 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
next prev parent reply other threads:[~2008-04-04 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 18:26 [PATCH] git-clone.txt: Adjust note to --shared for new pruning behavior of git-gc Brandon Casey
2008-04-03 19:14 ` Johannes Schindelin
2008-04-03 20:51 ` Brandon Casey
2008-04-03 20:01 ` Johannes Schindelin
2008-04-04 6:49 ` Jakub Narebski [this message]
2008-04-04 14:25 ` Brandon Casey
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=m3prt6t8sn.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.