how do I sell git to my colleagues?
mbrubeck: At both of my last two jobs, I helped switch my team from svn to git.  In both cases, at least of us first started using git-svn.  Other developers saw how we could use this to edit our commit history before pushing to the server; create lightweight topic branches to separate feature work from bug fixes; push changes from one personal repository to another for things like code reviews; and do better merges and cherry-picks between SVN branches than SVN itself.Other advantages to highlight are:
* Way better support for branches and merging, especially long-lived branches or any branches that include cherry-picked changes.  (SVN 1.5 improved things a lot, but we found that it still broke merges occasionally while git was rock-solid.)
* Great tools for offline/disconnected development (including commit, rollback, branch, history viewing, git-bisect).
* Increased speed of many common operations (viewing the log, merging and diffing across branches, switching branches, etc.)