Internals/Checkpoints

This is mostly for historical interest, as the ability to create new checkpoint patches was removed in Darcs 2.4

Checkpoint patches are the mechanism which allow darcs get –partial to work. Basically, the idea is to create a patch which is equivalent to a set of patches in its effect. The resulting patch is generally smaller (as self-cancelling or otherwise incremental patches go away) and avoids the problem of fetching many small patch files.

Unfortunately, it turned out that partial repositories were unreliable for many reasons.

As of Darcs 2, we now offer a better way of speeding up darcs get, which is to use hashed repositories and –lazy.

Notes

  • checkpoints created explicitly with darcs optimize –checkpoint (now gone)
  • checkpoint inventory contains just tags that darcs optimize –checkpoint was called on