Hi Ram, thank you for the reply. Se below . . . > >> I need some help getting my subversion repository cloned over to git. >> Our svn repository has about 12,000 commits, when I run >> git svn clone -s -A authors.txt >> svn+ssh://csvn <at> source.res.ourdomain.com/home/svn/sem sem >> It runs for about 2h 15m then completes with no error messages. I have >> also cloned starting at revision 6300, about the middle of the svn >> repository, and I get the same results as below. > >> $ git branch -a # shows only about half the branches that should have >> been cloned > > Interesting. From the git-svn-id of the most recent commit, can you > tell if there's anything especially fishy about the revision where > git-svn stops? Your Subversion repository is probably broken in some > way, but git-svn should not use that as an excuse for appearing to > finish successfully while failing in reality. Well by your question it seems you expect this clone to fail at the same svn revision number each time. I spent all day today trying to figure out what that revision was. However it doesn't seem to be failing at the same svn revision each time. There are about 12813 revisions in our svn repository so I started attempting clones from successively later and later revisions both to figure which revision they repeatedly failed on (it was never the same one) and to see if I could coax a successful clone to occur. Originally I started at revision 1, then incremented to 6300, then 8000, then 10000, then 12,500, then finally 12,700. Finally the attempt starting at svn revision 12,700 succeeded and the resulting git repository seems to work. All the attempts prior to 12,700 (starting at 1, 6300, 8000, 10000, and 12,500) failed while importing different revisions, none of them showed error messages. One thing that I am suspect of is that I'm not able to log directly into the machine running git, it's on a remote server in Atlanta while I'm in Colorado. I'm running the 'git svn clone' using nohup, but in every case of a corrupt git repository the connection between me and the server dies before the git completes (the connection dies, but I log in again and run ps -ef and I see the multiple git processes still running. They run for up to several hours longer, then terminate). I should be ok since I'm using nohup, but coincidentally the only clone that succeeded was the one where the network connection never disconnected during the clone Not sure if this helps but here are some numbers: Both the svn repository and git machine are Solaris 10 Svn revision 1.6.12 CollabNet Git version 1.7.6.1 Thank you. -- Steven Line 303-910-1212 sline00@xxxxxxxxx -- 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