Any reason to switch from svn to Git Version Control?

Question

I have long been a happy svn user. Recently, I often disconnect from my repository, so I am considering switching to Git.

Given the fact that I work alone in most of these projects. I am interested to know if Git is redundant for small projects? How much ahead of you? Is there a completely different workflow or an excellent learning curve?

Answer 1

I definitely recommend making a switch, but note that this will take some work. If you find yourself thinking, "Oh, [this git concept] is just like [this svn concept]!" be careful, because in reality it can be quite different. For example, svn revert means throwing uncommitted changes. git revert means creating a new commit that rolls back the changes that were introduced by one or more existing commits, such as svn "reverse-merge". The git command closest to svn revert is probably git checkout . In addition, many git commands act on the entire repository, while using the svn background you can expect them to work only with the current subdirectory.

Is git better? IMHO, absolutely yes. But are there any mistakes? Yes.

Answer 2

I think the only reason not to switch from SVN to git is when you need to learn the new system. Of course, if this were a very strong reason, we still used punch cards. IMHO, acquaintance is the only thing that SVN is going for him.

Answer 3

Git works great for small projects.

I have a small Lisp utility library here: https://github.com/pnathan/batteries . As you can say, this is tiny.

You will find that the workflow will be much more flexible, especially in the branch area. The learning curve was notoriously bad, but there are a lot of training aids.

Typically, your svn workflow can be easily done in git:

 workwork commit -a -m "my message" push goto workwork 

This will not use the full power of git, but it will satisfy your needs.

Answer 4

If you already own SVN, and often use it yourself, why not set up a local SVN repository? DVCS really shines with groups of people participating in the same project. If you don't encounter any common Subversion problem in your normal development cycle, why switch?

As I said, now I am much happier that I use DVCS (Mercurial) and, most likely, I will use it or Git even in solo projects. We switched because of problems with consolidation in SVN, so there was a legitimate problem that made us try a new system.