3 ms·
I often recommend people to read "Git Internals". If you know how git works internally, it's much easier to understand how it works and the reasons behind it.
by rubenbe 9y ago
I often recommend people to read "Git Internals".
If you know how git works internally, it's much easier to understand how it works and the reasons behind it.
https://git-scm.com/book/en/v1/Git-Internals https://git-scm.com/book/en/v1/Git-Internals
- nine_k 9y agoEven more enlightening is The git Parable. http://tom.preston-werner.com/2009/05/19/the-git-parable.html http://tom.preston-werner.com/2009/05/19/the-git-parable.htm...
- randomsearch 9y agoThis suggests a poor abstraction.
- goialoq 9y ago"Internals" is a poor choice of term. "Data structure" is a better term. Git is "plumbing and porcelain". The plumbing is the core of git. Porcelain are shortcuts. In general, Torvalds projects (Linux, Git) aren't big on abstractions that maximize simplicity-of-use, they focus on doing complex things correctly and quickly. Adding abstraction makes it hard to get details correct and run quickly.
- randomsearch 9y agoAgreed. Git seems like a good internal design with a terrible interface.