Thank you very much for your reply :-) Ahh, I didn't realise that that sort of SVN URL should be avoided. Is there any way around that when the project itself uses that sort of URL? And I think that it does require a username and empty password. I haven't tried the Github IRC channel - I must confess - I did not know that there was one. Any suggestions about how to deal with the other problem? The GitHub "Import a Subversion Repository" page does mention that you should try to avoid "svn://example.com/project/svn" style URLs (which SimuTrans uses). Maybe it's having trouble with needing a username & empty password? Unfortunately, I've never actually used the "Import from SVN" on GitHub. I see you've already posted to http://support.github.com/ about this. Have you tried asking in the GitHub IRC channel? On Sat, Mar 28, 2009 at 09:46, jamespetts <jamespetts@xxxxxxxxx> wrote: > > > > I just tried cloning this repo using the command below, and it appears > to be working just fine. (Hasn't finished, yet. Up to rev 465.) What > is the full command you're using when it will hang? > > I was not using the command line - I was using the GUI on the Github website. > -- > View this message in context: http://n2.nabble.com/Fork-of-abandoned-SVN-mirror---how-to-keep-up-to-date-with-the-SVN-tp2548952p2549665.html > Sent from the git mailing list archive at Nabble.com. > > -- > 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 > -- 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 -- View this message in context: http://n2.nabble.com/Fork-of-abandoned-SVN-mirror---how-to-keep-up-to-date-with-the-SVN-tp2548952p2549943.html Sent from the git mailing list archive at Nabble.com. -- 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
