Thank you for your reply. Unfortunately, I cannot for the life of me get git-svn to work. It refuses to recognise "git svn" as a valid command, and "svn" does not appear in the list of commands when I type, "svn --help" in Git Bash (I am using Git in Windows, if that makes any difference). I tried to look for svn2git, but the homepage linked from the link that you gave me produced a 404. Also, once I have managed to create a Git clone of the SVN repository myself, how do I synchronise that properly with the branch of the other mirror of the SVN repository that I have been using as the trunk so far, such that I can continue to download updates and have [i]just[/i] the changes since the previous versions applied? On Sat, Mar 28, 2009 at 11:06, jamespetts <jamespetts@xxxxxxxxx> wrote: > > 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? > It looks like GitHub won't keep the project in sync for you, so you're probably best off doing the git-svn clone yourself, and maintaining it that way. http://github.com/guides/import-from-subversion -- 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-tp2548952p2550565.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