What is git doing when it says it is “resolving deltas”?

by

The stages of git clone are:

  1. Receive a “pack” file of all the objects in the repo database
  2. Create an index file for the received pack
  3. Check out the head revision (for a non-bare repo, obviously)

“Resolving deltas” is the message shown for the second stage, indexing the pack file (“git index-pack”).

Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.

An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).

In summary, the “resolving deltas” stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.

In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message “resolving deltas” originated.

More Related Contents:

  1. How do I clone a specific Git branch? [duplicate]
  2. How do you clone a Git repository into a specific folder?
  3. Download a specific tag with Git
  4. How do I clone a subdirectory only of a Git repository?
  5. Are Git forks actually Git clones?
  6. What are the differences between git branch, fork, fetch, merge, rebase and clone?
  7. Why can’t I push from a shallow clone?
  8. How to convert a normal Git repository to a bare one?
  9. How to clone git repository with specific revision/changeset?
  10. Files showing as modified directly after a Git clone
  11. How to git-svn clone the last n revisions from a Subversion repository?
  12. How do I clone all remote branches?
  13. How do I clone a Git repository into a specific folder?
  14. How can I clone all remote branches?
  15. git hooks : is there a clone hook?
  16. Git clone: Redirect stderr to stdout but keep errors being written to stderr
  17. Clone A Private Repository (Github)
  18. What determines default branch after “git clone”?
  19. How to update a git clone –mirror?
  20. BitBucket – download source as ZIP
  21. How to clone a specific Git tag
  22. How to update a git shallow clone?
  23. Git clone with custom SSH using GIT_SSH error
  24. How to complete a git clone for a big project on an unstable connection?
  25. How to clone all repos at once from GitHub?
  26. Unable to Connect to GitHub.com For Cloning
  27. Why Isn’t There A Git Clone Specific Commit Option?
  28. How to get Git to clone into current directory
  29. git clone from another directory
  30. How to clone git repository from its zip

Leave a Comment