Re: git-fast-export hg mutt (24M vs 184M)

From: Pierre Habouzit <madcoder@debian.org>
Date: May 3, 2007, 22:29 UTC
Message-ID: <20070503222946.GH3260@artemis>
In-Reply-To: <20070503211824.GB16538@spearce.org>

On Thu, May 03, 2007 at 05:18:24PM -0400, Shawn O. Pearce wrote:

Show 14 quoted lines

> 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