Mercurial repository set up for GCC that mirrors SVN

[Daniel Berlin]

And today we learn why I think version control systems that think
"repacking" is something the user should be doing are worthless beasts
:)
It generally just means you didn't think through your storage
subsystem enough, but in git's case it's probably that the project it
was originally developed for just doesn't take a lot of disk space.

On 5/8/07, Harvey Harrison <harvey.harrison@gmail.com> wrote:
> git-svnimport will not pack incrementally as it runs, so it might get
> pretty large.  git-svn offers and incremental repack every x commits
> (I chose 1000) and that did wonders for the import time for me.
> Otherwise it will create a huge number of files before the final pack.
>
> Cheers,
>
> Harvey
>
> On 5/8/07, Ollie Wild <aaw@google.com> wrote:
> > > Just another data point, my git-svn clone of trunk comes in at 414MB,
> > > excluding the size of checked out files.  I'm assuming the public svn
> > > is the complete history.
> >
> > I'm about 35% through the process of cloning the entire gcc repository
> > via git-svnimport, and the .git directory is 5.0GB.  This includes all
> > branches.
> >
> > Danny, which of these matches what you've done with mercurial?
> >
> > Ollie
> >
>