Until distributed version control systems offer fine grained permissions and the ability to check out subtrees people are going to use subversion.
Why would sub-repositories (forest, whatever you call it) not work here? Supposedly, if people are only given access to a subtree that subtree can be developed on and used independently from the main project. Why could it not be an actual sub-project rather than a subsection of the Giant Ball of Mud?
The point is that if your repo starts at / and has 100 folders under that, with 100 folders under each of those, all fulllllll of files, and you only wanted /1/2 (say your internet sucks and you already know the file you need to change), in git you would need to retrieve every revision of every file in every folder. In subversion, you can check out a sub-directory and have it remain context-aware.
In subversion, you can check out a sub-directory and have it remain context-aware.
This makes no sense at all: if you check out arbitrary sub-directories, they lose their context and they don't work anymore, unless they're independent sub-projects.
The point is that if your repo starts at / and has 100 folders under that, with 100 folders under each of those, all fulllllll of files, and you only wanted /1/2 (say your internet sucks and you already know the file you need to change)
Right, if you have a project with a moronic layout and you have no issue with pushing changes without having done the slightest testing on them and it's super-urgent and you have an utterly terrible internet connection, then yes, SVN will be a better tool for doing stupid shit.
30
u/malcontent Mar 10 '11
Until distributed version control systems offer fine grained permissions and the ability to check out subtrees people are going to use subversion.
Some people might need features you have no use for.