On 20/02/2017 13:44, Marcel Reutegger wrote: > > Instead of the revision, the implementation can also rely on a > checkpoint that marks the snapshot of the repository as the basis of > the large-tree-operation.
I was thinking the same. We may rely on checkpoints and then store additional info the checkpoint itself (can we?) for resuming operations. I don't know if a diff computed against the empty (reindex) can change tree order on multiple runs and we may need to store somewhere the intermediate state of the reindexing so that by piking up: checkpoint, last path and indexed data we may resume correctly. D.
