clone: reuse the stream clone logic for local clone
Streaming clone and local (non `--pull`) clone do mostly the same thing, however they were using different logic to do so. This means the logic frequently went out of sync and that new case had to be dealt with twice. This is fragile and anoying. So we replace this with a re-use of the logic we use for streaming clone. I can see various test changes: - a more precise progress output, - armless fncache loading during clone, - fncache is no longer hardlinked (since we write it by hand). I am not reinstalling the `reposimplestore` specific output, as far as I understand this variant have been broken for years. Differential Revision: https://phab.mercurial-scm.org/D10855
Showing
- mercurial/hg.py 3 additions, 12 deletionsmercurial/hg.py
- mercurial/streamclone.py 106 additions, 0 deletionsmercurial/streamclone.py
- tests/test-clone.t 16 additions, 32 deletionstests/test-clone.t
- tests/test-empty.t 1 addition, 0 deletionstests/test-empty.t
- tests/test-fncache.t 4 additions, 0 deletionstests/test-fncache.t
- tests/test-hardlinks.t 12 additions, 12 deletionstests/test-hardlinks.t
- tests/test-subrepo-deep-nested-change.t 42 additions, 54 deletionstests/test-subrepo-deep-nested-change.t
- tests/test-subrepo-recursion.t 23 additions, 38 deletionstests/test-subrepo-recursion.t
Loading
-
mentioned in commit fe36a7c77f81
-
mentioned in commit c560c4ac4387
-
mentioned in commit b1e1559f5a45
-
mentioned in commit 2a61f7f01b1f
-
mentioned in commit 2cd00052ae4d
Please register or sign in to comment