##// END OF EJS Templates
repair: begin implementation of in-place upgrading...
repair: begin implementation of in-place upgrading Now that all the upgrade planning work is in place, we can start doing the real work: actually upgrading a repository. The main goal of this commit is to get the "framework" for running in-place upgrade actions in place. Rather than get too clever and low-level with regards to in-place upgrades, our strategy is to create a new, temporary repository, copy data to it, then replace the old data with the new. This allows us to reuse a lot of code in localrepo.py around store interaction, which will eventually consume the bulk of the upgrade code. But we have to start small. This patch implements adding new repository requirements. But it still sets up a temporary repository and locks it and the source repo before performing the requirements file swap. This means all the plumbing is in place to implement store copying in subsequent commits.

File last commit:

r9999:f91e5630 default
r30777:7de7afd8 default
Show More
hglogo.png
0 lines | 4.0 KiB | image/png | TextLexer
/ mercurial / templates / static / hglogo.png
rendered-image