Skip to content
Snippets Groups Projects
Commit 95a615dd77bf authored by Pierre-Yves David's avatar Pierre-Yves David :octopus:
Browse files

clone: make sure we warm the cache after a clone

This work around any deviciency/limitation of the clone process. In our case
this ensure the persistent nodemap exist with valid content.

Ideally, the cloning process would also do "the right thing". However since
older server will never be able to do "the right thing". The local workaround
will be necessary anyway.

I am not worried by the performance impact of this as `hg clone` is non-instant
on large repositories where is could matters. Warming the cache if they are
already correct is very fast. And if they are not already warm, this seems like
a good time to do so.

This impact various test as more cache are now warmed sooner, all the change
should be harmless.

Differential Revision: https://phab.mercurial-scm.org/D9789
parent 4cde46f62ebf
No related branches found
No related tags found
No related merge requests found
Showing with 135 additions and 20 deletions
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment