During the first clone of a repository, git first receives the objects (which is obvious enough), and then spends about the same amount of time \"resolving deltas\". What\'
Amber seems to be describing the object model that Mercurial or similar uses. Git does not store the deltas between subsequent versions of an object, but rather full snapshots of the object, every time. It then compresses these snapshots using delta compression, trying to find good deltas to use, regardless of where in the history these exist.