httppeer: only advertise partial-pull if capabilities are known
We don't need to be advertising client protocol parameters as part of the capabilities request during the handshake because nothing in version 1 of the wire protocol will use this data. i.e. the advertisement is wasteful. Differential Revision: https://phab.mercurial-scm.org/D3241
Showing
- mercurial/httppeer.py 5 additions, 1 deletionmercurial/httppeer.py
- tests/test-clonebundles.t 1 addition, 1 deletiontests/test-clonebundles.t
- tests/test-getbundle.t 2 additions, 2 deletionstests/test-getbundle.t
- tests/test-http-bad-server.t 9 additions, 29 deletionstests/test-http-bad-server.t
- tests/test-http-bundle1.t 21 additions, 21 deletionstests/test-http-bundle1.t
- tests/test-http-protocol.t 0 additions, 2 deletionstests/test-http-protocol.t
- tests/test-http-proxy.t 5 additions, 5 deletionstests/test-http-proxy.t
- tests/test-http.t 23 additions, 25 deletionstests/test-http.t
- tests/test-lfs-serve-access.t 2 additions, 2 deletionstests/test-lfs-serve-access.t
- tests/test-setdiscovery.t 1 addition, 1 deletiontests/test-setdiscovery.t
- tests/test-subrepo-deep-nested-change.t 2 additions, 2 deletionstests/test-subrepo-deep-nested-change.t
- tests/test-subrepo-recursion.t 9 additions, 9 deletionstests/test-subrepo-recursion.t
- tests/test-treediscovery.t 12 additions, 12 deletionstests/test-treediscovery.t
- tests/test-wireproto.t 22 additions, 22 deletionstests/test-wireproto.t
Loading
Please register or sign in to comment