phases: do not exchange secret changesets
Any secret changesets will be excluded from pull and push. Phase data are properly synchronized on pull and push if a changeset is seen as secret locally but is non-secret remote side. This patch does not handle the case of a changeset secret on remote but known locally.
Showing
- mercurial/discovery.py 18 additions, 2 deletionsmercurial/discovery.py
- mercurial/setdiscovery.py 2 additions, 1 deletionmercurial/setdiscovery.py
- mercurial/wireproto.py 2 additions, 1 deletionmercurial/wireproto.py
- tests/test-phases-exchange.t 63 additions, 1 deletiontests/test-phases-exchange.t
- tests/test-phases.t 46 additions, 0 deletionstests/test-phases.t
Loading
Please register or sign in to comment