From: skillzero@gmail.com
To: git@vger.kernel.org
Subject: Best way to optimize a git repository?
Date: Fri, 2 May 2008 17:34:02 -0700 [thread overview]
Message-ID: <2729632a0805021734h72196639x8789a00ce9be4059@mail.gmail.com> (raw)
I want to periodically optimize my repositories even if it takes a
long time to run the command. Should I do 'git gc --aggressive', 'git
repack -a -d', 'git prune', or some combination? The documentation
implies that things like git gc will use git repack, but I'm sort of
looking for the definitive answer of what I should run to fully
optimize my repositories. These are relatively new repositories, all
created with git 1.5.5.1.
I also read somewhere (but can't find now) that some of these commands
shouldn't be run while other people might be accessing the repository.
I want to run these commands on a server that multiple people clone
and pull from and push to. Is that safe to do? I'm okay if clone,
pull, or push fail during this time (although I'd prefer if they
didn't fail), I just don't want to corrupt the repository.
next reply other threads:[~2008-05-03 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 0:34 skillzero [this message]
2008-05-03 10:02 ` Best way to optimize a git repository? Stephen R. van den Berg
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=2729632a0805021734h72196639x8789a00ce9be4059@mail.gmail.com \
--to=skillzero@gmail.com \
--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).