We did that because after using git on top of Google Code's SVN backend (using git-svn) for a year or so, we were really limited by Subversion's lack of real br

We did that because after using git on top of Google Code's SVN backend (using git-svn) for a year or so, we were really limited by Subversion's lack of real brancing/merging. While on top of SVN, we only had two branches, and we did "lose" fixes done on one branch (as in forgetting to forward-port them to the other one) a few times. After switching to git, we're able to easily manage one master branch and two branches per release (so between 3 to 5 or more branches) easily, and with strong merging capabilities (no patches lost). Today Google Code also offers Mercurial, but we're so used to Git by now… :)