On 6/13/06, Daniel Berlin <dberlin@dberlin.org> wrote:
> Jon Smirl wrote:
> > On 6/13/06, Daniel Berlin <dberlin@dberlin.org> wrote:
> >> Jon Smirl wrote:
> >>> Another interesting tidbit.
> >>>
> >>> Mozilla CVS is 3.0GB
> >>> Same repository in svn is 8.2GB
> >>> Same repository in git is 680MB
> >>>
> >>> git does deltas and then compresses the deltas all into one giant
> >>> 680MB file. New commits are stored in collections of single files
> >>> until the repository is packed again.
> >>
> >> cvs2svn has significant problems with copy identification.
> >> If mozilla has a lot of branches, tons of them will end up with entire
> >
> > Is 1,800 a lot?
> >
>
> Yes.
>
> It is highly likely that almost all of your repo space is being taken
> up by identical new files that should have been copies, but cvs2svn
> borked it :)
>
> It is likely that git properly notices they are all the same data, and
> just shares them when you do a git to svn import.
>
> If you stare at the dumpfile that cvs2svn generates, and look at the
> commits that create your branches, you can see if it is properly making
> them copies or not.
>
> This is being attacked two fold, by working on fixing cvs2svn, and by
> working on issue 2286.
I've given up on this for a while. I'll try again when there is a new
cvs2svn release.
I lost power this morning while the city decided to move the telephone
pole in front of my house. That killed the import that had been
running for five days.
--
Jon Smirl
jonsmirl@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 21:07:45 2006