@toolforger said: Hm. I don't see the ability to discuss individual lines of code on Sourceforge. Using SVN to interact with git seems unwise to me, SVN simply can't reasonably map git's data model. Unless your drive the repository entirely from SVN and never allow git-based write access to the repo. I think it would be hard to enforce that rule though, so with the first slip you risk getting something that SVN isn't really happy about when displaying the history.
The recommenation against SVN is mostly a question of contributions. SVN gets slightly less useful with each contributor with write access, that’s all; SVN is just fine if you don’t have contributors and never experiment with ideas that you plan to scrap, or that you want to experiment with in parallel to normal ongoing work. (SVN is really bad at merging different branches. Or, rather, git and mercurial had to be top-notch on the merge tools due to their decentralized approaches, which turned out to be really essential even if you don’t do decentralized development, so now SVN is far behind.)
“Hi, I haven’t read anything about the integration but I’d be glad to offer detailed opinions.”
Thanks for the input. I will continue to use SVN to commit changes to JME.