changegroup: introduce cg3, which has support for exchanging treemanifests
I'm not entirely happy with using a trailing / on a "file" entry for transferring a treemanifest. We've discussed putting some flags on each file header[0], but I'm unconvinced that's actually any better: if we were going to add another feature to the cg format we'd still be doing a version bump anyway to cg4, so I'm inclined to not spend time coming up with a more sophisticated format until we actually know what the next feature we want to stuff in a changegroup will be. Test changes outside test-treemanifest.t are only due to the new CG3 bundlecap showing up in the wire protocol. Many thanks to adgar@google.com and martinvonz@google.com for helping me with various odd corners of the changegroup and treemanifest API. 0: It's not hard refactoring, nor is it a lot of work. I'm just disinclined to do speculative work when it's not clear what the customer would actually be.
Showing
- mercurial/changegroup.py 115 additions, 10 deletionsmercurial/changegroup.py
- tests/test-acl.t 54 additions, 54 deletionstests/test-acl.t
- tests/test-clonebundles.t 2 additions, 2 deletionstests/test-clonebundles.t
- tests/test-doctest.py 1 addition, 0 deletionstests/test-doctest.py
- tests/test-hgweb-commands.t 2 additions, 2 deletionstests/test-hgweb-commands.t
- tests/test-http-proxy.t 5 additions, 5 deletionstests/test-http-proxy.t
- tests/test-http.t 3 additions, 3 deletionstests/test-http.t
- tests/test-setdiscovery.t 1 addition, 1 deletiontests/test-setdiscovery.t
- tests/test-ssh-bundle1.t 2 additions, 2 deletionstests/test-ssh-bundle1.t
- tests/test-ssh.t 2 additions, 2 deletionstests/test-ssh.t
- tests/test-treemanifest.t 53 additions, 0 deletionstests/test-treemanifest.t
Loading
Please register or sign in to comment