> 2) At its very bottom, Git implements the so-called > "content-addressable filesystem". Its chief principle is that every > unique piece of data is stored exactly once, and these pieces are > identified by their contents. Since use the contents "as is" is > unwieldy, its being addressed using -- again -- the cryptographic hashes > calculated over those contents. This what makes Git effectively > implement its paradigm where each commit refers to a complete state of > all the project's files: even though like 99.9% of the content of each > commit a typical big project is the same as its parent commit, each > unique chunk of information -- a file or a tree referring to a set of > files -- is stored in the repository exactly once.
Content addressable filesystem. Nicely put. So, sort of content addressable memory (CAM) where contents are unique. Thanks a lot, -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
