From: Felix Natter <fnatter@gmx.net>
To: git@vger.kernel.org
Subject: git repack vs git gc --aggressive
Date: Tue, 07 Aug 2012 20:22:21 +0200 [thread overview]
Message-ID: <87zk66r28y.fsf@bitburger.home.felix> (raw)
hello,
I read this:
http://metalinguist.wordpress.com/2007/12/06/the-woes-of-git-gc-aggressive-and-how-git-deltas-work/
where
git repack -a -d --depth=250 --window=250
is mentioned as a (recommended) alternative to git gc --aggressive.
I am a bit confused, because the page also mentions that git gc --aggressive
is recommended when a repo has been imported using git fast-import.
So my questions are:
1. is the above repack command (with --depth=500) safe? Of course I want
to be absolutely sure that our repo will be consistent.
Do I need another command ("git gc", "git prune") as well?
2. is it the right tool for the job or shall I use git gc --aggressive?
Thanks!
--
Felix Natter
next reply other threads:[~2012-08-07 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 18:22 Felix Natter [this message]
2012-08-07 18:44 ` git repack vs git gc --aggressive Jeff King
2012-08-07 19:05 ` Junio C Hamano
2012-08-10 19:09 ` Felix Natter
2012-08-10 20:09 ` Junio C Hamano
2012-08-13 14:20 ` Marc Branchaud
2012-08-13 17:19 ` Junio C Hamano
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=87zk66r28y.fsf@bitburger.home.felix \
--to=fnatter@gmx.net \
--cc=git@vger.kernel.org \
/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).