Note the key advantages Git offered in each step:
1. Git creates a full repository with this command. With Subversion, you’re just checking out the files in the repository.
2. With each branch, no new files are created in the project file hierarchy on your system. Since you have a full local repository, Git creates the files you need on the fly by processing the recorded changes. With Subversion, you have to create every branch remotely on the server. This can get messy depending on the size of your team. If you decide to control branching to keep things clean, you forfeit the power branching offers.
3. With Git, we only push our work to the server AFTER collaboration (more below). With Subversion, it all hits the server.
4. Again, no file system work. Since we’re using a local repository, we let Git handle the details of removing the branch. With Subversion, you still have the old copy until you update. You either have to clean up manually, or “update” to clean up local and remote copies.(…)
Conclusion
There are literally hundreds of features for both Git and Subversion. While you may have detailed reasons to choose one over the other, I think these 3 high level reasons are strongly convincing in favor of Git. If you have differing opinions, I’d love to hear them.
- http://markmcb.com/2008/10/18/3-reasons-to-switch-to-git-from-subversion/
Post a Comment