2009/1/21 Kai Sterker <kai.ster...@gmail.com>: > Any opinions? For code git is great, but its not the perfect tool, it namely has these faults:
* no way to checkout just a subdirectory (narrow clone) * no way to checkout just the current revision instead of cloning the whole one (shallow clone) This means that having multiple projects in the same repository is much more troublesome then with SVN and it also means that having binary files in the code repository is a big fat no-no, since it would mean everybody has to download hundreds of megabyte instead of just a few for the engine source code. Luckily for both of these there is a SoC2009 proposal: * http://git.or.cz/gitwiki/SoC2009Ideas#head-d9c66dc80140e5d3530f032d30764212e7537f58 But that might take quite a while till its implemented. On the plus side git can handle local commits, makes branching easy and makes it easy to mirror the repository to multiple hosts, so switching providers or dual hosting is trivial. Git also has a github, which provide a great webinterface to a git repo: * http://github.com/ Conclusion? I don't really know. The lack of narrow cloning makes it impossible or at least extremely impractical to host the whole project in git. So if code goes to git, media would have to go to a seperate repository, likely an SVN one, due to SVN always doing narrow and shallow cloning (assuming that nobody wants to touch CVS ever again, I certainly haven't for quite some years). -- WWW: http://pingus.seul.org/~grumbel/ Blog: http://grumbel.blogspot.com/ JabberID: xmpp:grum...@jabber.org ICQ: 59461927 _______________________________________________ Adonthell-devel mailing list Adonthell-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/adonthell-devel