From: Pierre Habouzit <madcoder@debian.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Thomas Glanzmann <thomas@glanzmann.de>, GIT <git@vger.kernel.org>
Subject: Re: git-fast-export hg mutt (24M vs 184M)
Date: Fri, 4 May 2007 00:29:46 +0200 [thread overview]
Message-ID: <20070503222946.GH3260@artemis> (raw)
In-Reply-To: <20070503211824.GB16538@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
On Thu, May 03, 2007 at 05:18:24PM -0400, Shawn O. Pearce wrote:
> Pierre Habouzit <madcoder@debian.org> wrote:
> > On Thu, May 03, 2007 at 09:17:16PM +0200, Thomas Glanzmann wrote:
> > > Hello,
> > > git-repack -a -d -f got it down to 19M. I missed the -f parameter
> > > before. Sorry for the noise.
> >
> > You may want to use git gc that does that (and a bit more) for you.
>
> Actually, in this case, no.
>
> git-gc by default doesn't use the -f option. -f to git-repack
> means "no reuse deltas". That particular feature of git-repack is
> basically required to be used after running git-fast-import with
> anything sizeable.
okay, so why git fast-import does not let some note somewhere (to be
picked by git gc later) "a fast-import has been run, use -f for next
repack if you want best compression" ?
I'd think that would make a lot of sense, and that users that now
naively (like me) think git-gc would always be enough would not be
dramatically wrong ? :)
I mean it's nothing *very* important but some
`touch $GIT_DIR/info/unpacked-fast-import` in fast-import then:
if test -f $GIT_DIR/info/unpacked-fast-import; then
REPACK_OPTIONS=$REPACK_OPTIONS\ -f
fi
// do the repack
rm -f $GIT_DIR/info/unpacked-fast-import
would do the trick, wouldn't it ?
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-03 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 18:56 git-fast-export hg mutt (24M vs 184M) Thomas Glanzmann
2007-05-03 19:17 ` Thomas Glanzmann
2007-05-03 21:01 ` Pierre Habouzit
2007-05-03 21:18 ` Shawn O. Pearce
2007-05-03 22:29 ` Pierre Habouzit [this message]
2007-05-04 1:11 ` Nicolas Pitre
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=20070503222946.GH3260@artemis \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=thomas@glanzmann.de \
/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).