Re:Git koans
by philwelch on Monday April 08, 2013 @02:57PM
(#5513711)
Git is predicated on the notion that it's actually quite simple and elegant how Git works, and programmers are clever enough to understand how their software works, so not much porcelain is necessary. There's a refreshing honesty to that.
[ Parent
| on HN ]
That's not my understanding of it's history; it was originally planned to have, potentially, multiple porcelains, but that idea died of a couple years back.
It was discovered more or less by accident, I think. Similar to the story of M-expressions in Lisp: http://en.wikipedia.org/wiki/M-expression
I believe that is the root problem of git. Originally, the assumption was: porcelains will provide a nice UI, so core git can leak implementation details. However, it turns out the implementation details are so simple and intuitive for many developers that core git is now the dominant UI.
For example, the multiple use cases of 'checkout' or 'reset' are quite intuitive, if you have the implementation in mind.
I have no idea how git works. Where do they tell you? I'm curious to learn.
I have found the Pro Git book to be the best:
http://git-scm.com/book
That, and constantly creating your own test repositories to test new commands/concepts. With a distributed VCS it's easy and fast. Just run "git init test" somewhere and start committing!
I also recommend you to use "gitk" when you're learning to constantly look at your history tree. That should clarify the concept "branches are pointers" after a few tests.
Git for computer scientists: http://eagain.net/articles/git-for-computer-scientists/
Quick introduction to git internals for people who are not scared by words like Directed Acyclic Graph.