From: "Shawn O. Pearce" <spearce@spearce.org>
To: Geert Bosch <bosch@adacore.com>
Cc: Jeff King <peff@peff.net>, Nicolas Pitre <nico@cam.org>,
Brandon Casey <casey@nrlssc.navy.mil>,
John Dlugosz <JDlugosz@TradeStation.com>,
git@vger.kernel.org
Subject: Re: dangling commits and blobs: is this normal?
Date: Thu, 23 Apr 2009 10:56:13 -0700 [thread overview]
Message-ID: <20090423175612.GV23604@spearce.org> (raw)
In-Reply-To: <064C9132-2E72-4665-A44D-A2F4194DAC2B@adacore.com>
Geert Bosch <bosch@adacore.com> wrote:
> significant
> speedups, especially during large imports that currently require
> frequent
> repacking of the entire repository.
Large imports should be using fast-import, and then issue a single
massive `git repack -f --window=250 --depth=50` or some such repack
command after the entire import is complete.
If your favorite import tool (*cough* git-svn *cough*) can't use
fast-import, and you are importing a large enough repository that
this matters to you, use another importer that can use fast-import.
--
Shawn.
next prev parent reply other threads:[~2009-04-23 17:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 21:46 dangling commits and blobs: is this normal? John Dlugosz
2009-04-22 15:27 ` Jeff King
2009-04-22 16:53 ` Brandon Casey
2009-04-22 17:39 ` Nicolas Pitre
2009-04-22 18:15 ` Matthieu Moy
2009-04-22 19:08 ` Jeff King
2009-04-22 19:45 ` Brandon Casey
2009-04-22 19:58 ` Jeff King
2009-04-22 20:07 ` Nicolas Pitre
2009-04-23 11:51 ` Matthieu Moy
2009-04-22 19:14 ` Nicolas Pitre
2009-04-22 19:26 ` Brandon Casey
2009-04-22 20:00 ` Nicolas Pitre
2009-04-22 20:05 ` Jeff King
2009-04-22 20:11 ` Nicolas Pitre
2009-04-23 17:43 ` Geert Bosch
2009-04-23 17:56 ` Shawn O. Pearce [this message]
2009-04-23 18:10 ` Geert Bosch
2009-04-23 18:17 ` Matthias Andree
2009-04-23 18:51 ` Nicolas Pitre
2009-04-22 20:15 ` John Dlugosz
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=20090423175612.GV23604@spearce.org \
--to=spearce@spearce.org \
--cc=JDlugosz@TradeStation.com \
--cc=bosch@adacore.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=peff@peff.net \
/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).