Shawn O. Pearce wrote: > If we are heading in the direction of making this a common stream > format I'd like to try and work it out such that any additional > extensions aren't VCS specific, at least as much as we can avoid it. > That way exports from a source into this format can be loaded into > any VCS that recognizes it, and have little or no loss. So yes, > I am interested in trying to work with you and anyone else who wants > to extend the format further. Excellent. That sounds the right way to go. I'll contact you if and when I want to add stuff. > Heh. OOo is _huge_. I think the best import into Git thus far is > taking up about 1.5G of disk space once fully repacked. I don't > recall how they did the import, but coming from SVN I think they > used git-svn, which is not based on git-fast-import. > > What frontend are you using to go from SVN -> fast-import? The pack file in the Git clone I have is 2.4G. I thought that was large but it's quite small compared to the 82G svn dump that creates a 55G svn repo! I'm using svn-fast-export.c currently. I'd rather enhance the Python one but my Subversion binding knowledge is slim and there's a bug wrt "too many open files" that causes it to crash almost immediately on the OOo repo. It's not obvious to me how to fix that unfortunately. It worked fine for Wordpress OTOH. The svn-all-fast-export tool sounds interesting but is completely undocumented to my knowledge. Ian C. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
