##// END OF EJS Templates
wireprotov2: allow multiple fields to follow revision maps...
wireprotov2: allow multiple fields to follow revision maps The *data wire protocol commands emit a series of CBOR values. Because revision/delta data may be large, their data is emitted outside the map as a top-level bytestring value. Before this commit, we'd emit a single optional bytestring value after the revision descriptor map. This got the job done. But it was limiting in that we could only send a single field. And, it required the consumer to know that the presence of a key in the map implied the existence of a following bytestring value. This commit changes the encoding strategy so top-level bytestring values in the stream are explicitly denoted in a "fieldsfollowing" key. This key contains an array defining what fields that follow and the expected size of each field. By defining things this way, we can easily send N bytestring values without any ambiguity about their order. In addition, clients only need to know how to parse ``fieldsfollowing`` to know if extra values are present. Because this breaks backwards compatibility, we've bumped the version number of the wire protocol version 2 API endpoint. Differential Revision: https://phab.mercurial-scm.org/D4620

File last commit:

r26421:4b0fc75f default
r39839:d059cb66 default
Show More
postinstall.txt
9 lines | 248 B | text/plain | TextLexer
Bryan O'Sullivan
Add post-install text file.
r1289 Welcome to Mercurial for Windows!
---------------------------------
For configuration and usage directions, please read the ReadMe.html
file that comes with this package.
Matt Mackall
Remove hard-coded version numbers and release notes from packaging
r3863 Also check the release notes at:
Lee Cantey
Update Windows release notes and install script for v0.9
r2276
Matt Mackall
urls: bulk-change primary website URLs
r26421 https://mercurial-scm.org/wiki/WhatsNew