Furthermore, Mercurial tries to cater to users of other VCSes, distributed or not, because it wants to present a consistent interface. Git makes no such concession.

*bangs head on wall*

So far, I’ve had GIT commit the one file out of 3,000 that I wanted. When I looked at our remote GIT repository, it deleted 2,999 files and updated the one I changed. Fantastic.

luckily, our subversion repo is still around so I didn’t really lose anything.

Not sure if I found this on your site or someplace else, but it describes how easy it is to use GIT for a simple, 2 developer, non open source, project. In subversion, I change a file, I commit. that apparently is too difficult. Luckily, GIT has a much simpler work flow for us now:

“That is one of the simplest workflows. You work for a while, generally in a topic branch, and merge into your master branch when it’s ready to be integrated. When you want to share that work, you merge it into your own master branch, then fetch and merge origin/master if it has changed, and finally push to the master branch on the server.”