I think what the author's getting at with respect to git's mental model is that commits form a directed graph, with each commit pointing to its parent (or parents, in the case of merge commits), and with "branches" just functioning as names that point to a particular commit. The gnarly set of git commands do operations on this directed graph, and that's basically it.
The model is relatively simple, but having in mind what you are trying to do to the graph of commits goes a long way in figuring out the sequence of commands one might use to get there. _______________________________________________ Discuss mailing list Discuss@lists.software-carpentry.org http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
