{"thread":{"id":"23710","subject":"svn repo a submodule?","startedAt":"2010-05-05T14:43:20Z","lastAt":"2010-05-05T14:43:20Z","messageCount":1,"participants":["Samir Faci"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"140993","messageId":"g2i9db93b0e1005050743q43d745ebod1aa13f98ab5a44c@mail.gmail.com","threadId":"23710","inReplyTo":null,"subject":"svn repo a submodule?","fromName":"Samir Faci","fromEmail":"samir@esamir.com","sentAt":"2010-05-05T14:43:20Z","receivedAt":"2010-05-05T14:43:20Z","isPatch":false,"sender":{"key":"samir@esamir.com","avatar":null},"body":"I've been using git submodule to refer to external repos that I don't\nmaintain.  (which works great)\n\nSo far in order to use an svn repo as a submodule I end up doing a git\nsvn clone, and basically have a crontab job that pulls from svn and\npushes to git repo.  Then I end up using the git repo it creates as a\ngit submodule.\n\nThe workflow does work, though it is a bit tedious.   I was wondering\nif there was any particular reason why having an svn repo as a\nsubmodule isn't supported at this time.  Or if there was a better way\nof accomplishing this that escapes me.\n\n\n--\nSamir Faci\n*insert title*\nfortune | cowsay -f /usr/share/cows/tux.cow\n"}]}