7 ms·
The best (known to me) informal intro into the architecture of Git is The Git Parable: http://tom.preston-werner.com/2009/05/19/the-git-parable.html http://tom.
by nine_k 8y ago
The best (known to me) informal intro into the architecture of Git 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...
- svat 8y agoAlso greatly worth reading: “Git from the Bottom Up”: * HTML version: https://jwiegley.github.io/git-from-the-bottom-up/ https://jwiegley.github.io/git-from-the-bottom-up/ * PDF version: http://ftp.newartisans.com/pub/git.from.bottom.up.pdf http://ftp.newartisans.com/pub/git.from.bottom.up.pdf (via http://newartisans.com/2008/04/git-from-the-bottom-up/ http://newartisans.com/2008/04/git-from-the-bottom-up/) The great thing is that after reading and understanding these, one's mental model matches the reality of the Git program, so one can both try bolder things, and get unstuck from any mess.
- freshhawk 8y agoI recommend this constantly, it is excellent. Not to outright beginners, but anyone past that point should read this. It is a great job of clearly presenting an accurate mental model that helps you use git. If you are already a git expert this is just a good thing to learn from in general and with how to explain and teach git usage in particular. The only documentation I know of that can turn people from cargo cult git users to people who just do the version control things they need done with the parts of git they need. That is damn useful.
- paulddraper 8y ago> After using branches for a while you notice that they can serve two purposes. The first use case allows you to keep track of ongoing development, things like “Release Maintenance”. The second case is useful for labeling points of interest, like “Version 1.0” and “Version 1.0.1”. > For the sake of clarity and elegance, you decide to create another file called tags to contain pointers of the second type. Keeping these two inherently different pointers in separate files will help you from accidentally treating a branch as a tag or vice versa. Ah, ha ha ha ha ha ha ha ha ha ha ha. If "tags" and "branches" were the same thing, but just conventionally separate uses, that would be great. If only that was the way git treated them.
- dang 8y ago> Ah, ha ha ha ha ha ha ha ha ha ha ha Would you please not post like that here? It degrades discussion. The rest of your comment is ok, though the reader would learn more if you explained what the problem actually is.
- malingo 8y agoI've always liked the low-level explanation at https://git-scm.com/book/en/v2/Git-Internals-Git-Objects https://git-scm.com/book/en/v2/Git-Internals-Git-Objects It's a great exercise for the reader to recreate the core functionality of making git commits with just a few command line utilities (echo, wc, xxd, shasum).
- alexchamberlain 8y agoIIRC,that's how they were implemented in the first place.