One of Git's great features is a bidirectional bridge to Subversion called git svn. This tool allows you to use Git as a valid client to a Subversion server, so you. git svn can track a standard Subversion repository, following the common "trunk/ branches/tags" layout, with the --stdlayout option. It can also follow branches and . In those small tables, at the left we always list the Git commands for the task, while at the right the corresponding Subversion commands you would use for the .
Subversion (SVN) repositories are similar to Git repositories, but there are several differences when it comes to the architecture of your projects. . What I also see are Git-SVN Bridges: The central repository is a Subversion repo, but developers locally work with Git and the bridge then pushes their changes. What are the major differences between Git and SVN, and why do we choose Git ? Explore the pros and cons.
Scott Chacon of Github explains why you should ditch subversion for git. The site is intended to dispel myths about Subversion and Git. Although it doesn't tell which VCS is better, it helps you to understand the actual. Actually, switching from Subversion to Git isn't very complicated - but only if you Subversion is a centralized version control system: all team members work. Forget Git, just use Subversion (or Perforce). TL;DR If you're a small team creating a single product and want to make fast progress, you don't.