##// END OF EJS Templates
cg4: introduce protocol flag to signify the presence of sidedata...
cg4: introduce protocol flag to signify the presence of sidedata We need a way of signaling whether the current revision has sidedata or not, and re-using the revision flags would waste potential revlog flags and mix two normally independent layers. In this change, we add a single byte at the start of the ch4 delta header to set potential protocol flags. We also reclaim the revlog flag for sidedata, since it is no longer used, in its place now lives the (also experimental) copytracing flag. When generating deltas, apply the `CG_FLAG_SIDEDATA` flag if there is sidedata. When applying the deltas, if said flag is present, the next chunk contains the sidedata. Differential Revision: https://phab.mercurial-scm.org/D10343
Raphaël Gomès -
r47843:119790e1 default
Show More
Name Size Modified Last Commit Author
/ mercurial / helptext / internals
__init__.py Loading ...
bid-merge.txt Loading ...
bundle2.txt Loading ...
bundles.txt Loading ...
cbor.txt Loading ...
censor.txt Loading ...
changegroups.txt Loading ...
config.txt Loading ...
extensions.txt Loading ...
linelog.txt Loading ...
mergestate.txt Loading ...
requirements.txt Loading ...
revlogs.txt Loading ...
wireprotocol.txt Loading ...
wireprotocolrpc.txt Loading ...
wireprotocolv2.txt Loading ...