stream-clone: allow to change persistent-nodemap format during stream clone
Persistent nodemap affect the store format. However it is fairly isolated and fast to generate locally. So not making it a fixed part of the stream clone is useful. This allow clients without persistent-nodemap support (default for client without Rust enabled, or simply older client). So it make it possible to enable persistent nodemap on client, where it can provide a massive boost. without too much consequence. To do so, we stop using it in the advertisement requirements for streaming and let the client add/remove the necessary file depending of its configuration. We still send the files as it seems like a small save to not regenerate them. In addition, the way we match them will overlap with the changelog-v2/revlog-v2 so we can't simply skip the associated patterns. Differential Revision: https://phab.mercurial-scm.org/D12096
Showing
- mercurial/requirements.py 0 additions, 1 deletionmercurial/requirements.py
- mercurial/revlogutils/nodemap.py 14 additions, 0 deletionsmercurial/revlogutils/nodemap.py
- mercurial/streamclone.py 6 additions, 0 deletionsmercurial/streamclone.py
- tests/test-bundle.t 13 additions, 13 deletionstests/test-bundle.t
- tests/test-clone-stream-format.t 89 additions, 1 deletiontests/test-clone-stream-format.t
- tests/test-clone-stream.t 14 additions, 14 deletionstests/test-clone-stream.t
- tests/test-clonebundles.t 1 addition, 1 deletiontests/test-clonebundles.t
- tests/test-debugcommands.t 2 additions, 2 deletionstests/test-debugcommands.t
- tests/test-stream-bundle-v2.t 2 additions, 2 deletionstests/test-stream-bundle-v2.t
Loading
Please register or sign in to comment