Git from the Bottom Up (2009) [pdf]
ftp.newartisans.com
Git from the Bottom Up (2009) [pdf]
1–10 of 26 posts
Re: Git from the Bottom Up (2009) [pdf]
#2Seems to be down ATM.
Archive link: http://web.archive.org/web/20150906053023/http://ftp.newarti...
Re: Git from the Bottom Up (2009) [pdf]
#3This is the right way to learn Git. I don't know how good this is, but I feel most of the strange unintuitiveness of git went away and was replaced by a feeling of productivity since I understood what happens under git's hood.
Re: Git from the Bottom Up (2009) [pdf]
#4Related: https://git-scm.com/book/en/v1/Git-Internals-Git-Objects (and other sections in that chapter)
Re: Git from the Bottom Up (2009) [pdf]
#5Web version: http://jwiegley.github.io/git-from-the-bottom-up/
A nice resource in the same vein -- build a bare bones git in javascript: http://kushagragour.in/blog/2014/01/build-git-learn-git/
And finally, Linus's one page explanation of git's central concepts for the initial commit of git: https://github.com/git/git/tree/e83c5163316f89bfbde7d9ab23ca...
Re: Git from the Bottom Up (2009) [pdf]
#6Old but gold. This is how I learned git, and I think it's the only proper way.
Actually I did `git help tutorial` first to get started.
Re: Git from the Bottom Up (2009) [pdf]
#7This is the right way to learn Git. I don't know how good this is, but I feel most of the strange unintuitiveness of git went away and was replaced by a feeling of productivity since I understood what happens under git's hood.
The big take away for me was the idea of blobs and trees as Hickeyian values and commits as Von Neumann places. [1] If there is one weakness is the article it is ending with stash, which to me seems to be a bit of a feature in search of a workflow more than something that enhances distribution and sharing among a team in so far as the class of problem it addresses seems to result from larger issues of team structure and workflow [if it's worth saving then the whole team should know about it and have access].
It's useful to know about, but placing it at the end makes it seem like a high order bit rather than something for a corner case.
Re: Git from the Bottom Up (2009) [pdf]
#8Related: https://git-scm.com/book/en/v1/Git-Internals-Git-Objects (and other sections in that chapter)
This chapter was updated for the 2nd edition:
Re: Git from the Bottom Up (2009) [pdf]
#9Related, for visual learners, Git for ages 4 and up: https://www.youtube.com/watch?v=1ffBJ4sVUb4
Re: Git from the Bottom Up (2009) [pdf]
#10This is the right way to learn Git. I don't know how good this is, but I feel most of the strange unintuitiveness of git went away and was replaced by a feeling of productivity since I understood what happens under git's hood.
The big take away for me was the idea of blobs and trees as Hickeyian values and commits as Von Neumann places. [1] If there is one weakness is the article it is ending with stash , which to me seems to be a bit of a feature in search of a workflow more than something that enhances distribution and sharing among a team in so far as the class of problem it addresses seems to result from larger issues of team structure…
I find stash useful primarily as a place to hold things for a few minutes, and no longer. In particular, I frequently use "git stash", followed by "git pull --rebase", and if all went well, "git stash pop". I could just as easily do "git commit -a -m 'WIP'", "git pull --rebase", and "git reset HEAD^", but I find stash more intuitive.