{"thread":{"id":"8638","subject":"git tool to keep a subversion mirror","startedAt":"2007-06-18T14:47:31Z","lastAt":"2007-06-18T14:47:31Z","messageCount":1,"participants":["Sergey Yanovich"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45270","messageId":"11821780511231-git-send-email-ynvich@gmail.com","threadId":"8638","inReplyTo":null,"subject":"git tool to keep a subversion mirror","fromName":"Sergey Yanovich","fromEmail":"ynvich@gmail.com","sentAt":"2007-06-18T14:47:31Z","receivedAt":"2007-06-18T14:47:31Z","isPatch":false,"sender":{"key":"ynvich@gmail.com","avatar":null},"body":"Johannes Sixt wrote:\n> It is extremely difficult to tell whether the patch makes sense or is\n> correct, if there is _no_ explanation what it is good for.\n\nI agree 100%. I sent a fore-letter using git-send-email, but all parts got split. \n\nPasting it manually:\n\n> I am actively using git for my project. Thanks everyone envolved.\n> \n> However, I got tired of administering own web server and registered my\n> project at sourceforge. Unlike repo.or.cz (thanks again for everyone\n> envolved), they do not provide git hosting. But a project without a\n> source repository is non-sence.\n> \n> I am not in any way going to use Subversion after I tried git, but I\n> need to be able to export to a Subversion repository. I found an\n> excellent tool called 'git-svn'. However, the flawed nature of\n> Subversion put shackles on normal git usage after you do 'git-svn init'.\n> \n> Since git is the best scm system, my situation is probably quite common.\n> So I am filing these patches.\n> \n> There is a 'git-svn' command which does want I need, so I created a\n> simple wrapper around it. I also found that 'git-svn commit-diff' is\n> having a small trouble dealing with root <tree-ish>, which is corrected\n> by an attached patch.\n"}]}