3 ms·

we have an external svn reference in core to table layout, something git doesn't support. your best bet is to check out libgdx from svn to et the externals. it

• eropple 14y ago
  That's good to know, and I'm really trying not to look a gift horse in the mouth because libgdx is awesome, but you should probably know that saying "use SVN" is really close to saying "don't contribute to my project." libgdx is literally the only project I use that uses SVN and I almost didn't use it because SVN makes hacking on code viciously unpleasant.
  • badlogic 14y ago
    Massive amount of edits on your end, not sure what i'm replying to. Glad the middlefinger was removed, i'm afraid i won't be availble for a SVN vs. Git war. We have our reasons to use SVN for the time being, externals being one of them (git modules don't work for our setup), tooling support being another one. We are eager to give people commit rights, provided they follow a small set of rules. This does not necessarily help you with your dev process of having lots of local changes that you throw away. But that's something git-svn should be able to solve. Ping me via e-mail at contact at badlogicgames dot com.
    • deleted 14y ago
      [deleted]
  • flatline3 14y ago
    If you're that upset about a perfectly functional SCM system, you're acting like a person who is 'visciously unpleasant' to deal with. SVN is functional, simple, and it works. If you're doing OSS contribution right, you'll spend far more time talking and coding than you'll spend poking at SCM, and you won't be maintaining a large fork or poor hacks that upstream doesn't want to merge. Discuss early, merge often.