On Wed, 2009-12-16 at 00:15 -0800, Eric Wong wrote: > Mark Jerkovic <mjerkovic@xxxxxxxxxx> wrote: > > Hi all, > > > > I am new to Git and I am attempting to clone a SVN repository > > (containing approximately 60,000 commits) to Git. > > > > Using Git v1.6.0.4 with the following command: > > > > git svn clone https://path/to/svn/repo/trunk project.git > > --authors-file=svnauthors.txt --no-metadata > > > > the process just ends without any messages and the Git repository is > > empty. I have attempted this four times already, and each time it has > > stopped after a different revision, so I can't pin it down to a > > particular commit. > > Hi Mark, > > Any chance you're OOM-ing (extremely large file) or running > out of space somewhere? What exit code do you get when it exits? > > > Has anyone experienced this before? Is there a log anywhere that > > records what is happening during this process? > > Not without error messages of some sort. git svn was designed with poor > network conditions in mind and clone is resumable, so you can just > resume like this: > > cd project.git && git svn fetch > That is an excellent tip. Thanks a lot! > I wouldn't use --no-metadata at this point, though, as it makes it much > harder to debug/fix things or recover from errors. > > Once you're comfortable with it, you should be able to write > "git filter-branch" invocation to remove the metadata lines. I have done some more investigating and it appears that at some point a branch was moved to replace our trunk. When the migration process hits this I it goes back to the beginning and starts migrating the branch history too. I think when it gets to the end of it is not able to resume from the "move" point. I will try your resume tip to see if I can get it started again. Many thanks, Mark. > -- 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