Previously, I blogged about using Git with Subversion. Sometimes though, I like concise pieces of information, without all the details. For that reason, here is a cheatsheet on the steps for using Git with Subversion:
I recently started a new job where the team is using Subversion as its VCS. Coming from a previous job that used Mercurial, I found myself missing a DVCS. The main reason that I miss a DVCS really comes down to how I like write code. My preferred workflow is to constantly work in small iterations, constantly reshaping, manipulating code, until I’m happy with the final implementation. This is often coupled with committing changes to my local repository at various “milestones” along the way, so that I have snapshot of my work, and so that I can move back to a previous “state”, if I ended up exploring a path that didn’t turn out as expected. This kind of workflow really can’t be done in Subversion since every commit is to the central repository. This is where Git and Mercurial shine. I didn’t want to give up my current coding style, and decided to learn how to use a DVCS with Subversion. I chose Git because it seemed to have better support and community information on how to use it with Subversion.