2 ms·
1) Git's vocabulary is bizarre. 2) Every tutorial and book leans into the horrible vocabulary, and the metaphors they use to "simplify" and "explain" it only m
by pessimizer 4y ago
1) Git's vocabulary is bizarre.
2) Every tutorial and book leans into the horrible vocabulary, and the metaphors they use to "simplify" and "explain" it only make it worse. All of the analogical baggage is far more complicated than a straightforward description of the data structures.
It took an embarrassingly long time for me to understand that HEAD was just a pointer at the branch or commit you were currently working with (I wish somebody would take that "detached HEAD" terminology out back and shoot it), and that a branch was just a tag that, if HEAD is pointing at it, will move to point to a new commit that you make.
That's because "HEAD" and "branch" are stolen terms crowbarred into something quite different than CVS.
edit: the actual Git book from git-scm.com is not bad at all, but most people aren't learning from that.