I don't really recommend that approach, personally. First, I disagree with the statement at the top of the page that you can think of Git as CVS or Subversion

I don't really recommend that approach, personally. First, I disagree with the statement at the top of the page that you can think of Git as CVS or Subversion "without the cruft." In fact, Git is fundamentally different. Second, I think it's important to have a good conceptual understanding of Git. You can't just learn how to interact with it; you'll get confused and not be able to use its full power. Joel on Software directly addresses both of these points in a recent blog post [1] (which I probably found originally via HN). [1] http://www.joelonsoftware.com/items/2010/03/17.html http://www.joelonsoftware.com/items/2010/03/17.html