This can be done just as well with git-svn.
All the arguments pro git you bring also apply if git-svn is used on a svn master repository.
And as long as this is the case, I see no single reason to switch SCM.
Moderators: Nexuiz Moderators, Moderators
Well, then you want to practice what Linus does with the linux kernel? devs send him pull requests or patches per mail and he integrates them if he thinks they are okay. This is one of the development ways git was made for...divVerent wrote:LOL.
Someone has to check it, or the code base gets as bad as it once was again, with commits by people I won't name here.
Which is why I maintain that "stable branch" of Nexuiz.
Psychcf wrote:Woah, everyone went crazy while I was gone.
Let me just re-iterate this point... I notice a lot that people are doing more and more 3rd party mods (myself included), and I'm just suggesting that git would make merging said changes a lot easier, and would encourage people to get their work into the main repo.
Also, we don't need to choose between one or the other! Git-svn allows us to keep an SVN repo and a git repo in sync with each other, so those who still want SVN can stick with SVN, while everyone willing to try something new can use Git.
Psychcf wrote:Woah, everyone went crazy while I was gone.
Let me just re-iterate this point... I notice a lot that people are doing more and more 3rd party mods (myself included), and I'm just suggesting that git would make merging said changes a lot easier, and would encourage people to get their work into the main repo.
Also, we don't need to choose between one or the other! Git-svn allows us to keep an SVN repo and a git repo in sync with each other, so those who still want SVN can stick with SVN, while everyone willing to try something new can use Git.
Return to Nexuiz - Development
Users browsing this forum: No registered users and 1 guest