Figure 1 shows this classic model of source control with a centralized server and many users working against the repository on it. This model provides collaboration by having everyone work against the same server, with all of their work being visible to everyone else upon commit. Users who wish to work against that repository will bring a copy of what they need down to their local computer, make the necessary changes, and then commit the changes directly to the repository on the server. Subversion-among many other popular source-control systems such as CVS and Team Foundation Server-solves these problems using a centralized repository model. Having a basic understanding of where and how Subversion and Git differ will offer insights into working with Git and why certain actions and commands are necessary.

While there are a number of ideas that transfer from Subversion to Git, there are also a number of ideas in Git that will not have an equivalent. It is also necessary to understand the differences and to look at some of the features that Git provides, for which Subversion has no equivalent.

However, understanding the similarities alone will not be sufficient for learning Git. Understanding how these systems are similar can be important for those with experience using Subversion who want to learn Git. There are still other similarities, as well. They both support branching, merging, and working with files without locking them. They are both popular and are open source, proving integration points for other development-related tools. They are both source-control systems that work on nearly every modern development platform. There are some similarities between Subversion and Git.

Why are git gui tools frowned upon