A very large portion of the 9 days we've spent working on this project has been spent setting up and learning a lot of new software. No piece of software that we have tackled has been remotely as challenging as Git. We are using Git via the Eclipse plug-in EGit. The user interface is bad, and we have not found any reasonable tutorials to explain what the basic model and operating procedures are. We wasted many hours being defeated by EGIt/Git. Even when we struggled though and got what we wanted to happen, we were often unable to repeat it the next time. The experience was infuriating - I don't often use foul language, but I was sorely tested by Git.
I believe Git itself is somewhat challenging. Googling around for solutions and help, I have found POSTs from numerous folks who are struggling and a few who have given up on Git in disgust. Still, Git has become wildly popular, so I have to believe that the general experience that people have had is better than ours. One (unproven) hypothesis I have is that Eclipse.EGit actually makes the experience much worse. If you know exactly what you are doing with Git itself, I think you might be able to figure out how to use Git through EGit, but if you are trying to learn with EGit, the experience is horrible. The developers of EGit (Aptana, I think) are presumably trying to protect our SCM business in RTC. I suspect, but cannot prove, that if we had just used Git from the command line we would have been much happier, at least until we had really learned the concepts, terminology and workflows.