This is an archive of the discontinued Mercurial Phabricator instance.

Status	Author	Revision
Closed	marmoute	D6898 sidedata: check that the sidedata safely roundtrip
Closed	marmoute	D6897 sidedata: add a debugsidedata command
Closed	marmoute	D6896 sidedata: test we can successfully write sidedata
Closed	marmoute	D6895 sidedata: make sure we don't use the flag if there are not sidedata
Closed	marmoute	D6894 revlog: add the appropriate flag is sidedata are passed to `addrevision`
Closed	marmoute	D6893 sidedata: register the flag processors if the repository allows for it
Closed	marmoute	D6892 sidedata: add a function for _processflagsraw usage
Closed	marmoute	D6891 sidedata: add a function to write sidedata into a raw text
Closed	marmoute	D6890 sidedata: add a function to read sidedata from revlog raw text
Closed	marmoute	D6889 sidedata: add a new module with basic documentation
Closed	marmoute	D6888 sidedata: add a new revision flag constant for side data
Closed	marmoute	D6887 upgrade: detect the side-data format variants
Closed	marmoute	D6886 sidedata: introduce a new requirement to protect the feature

Diff 16761

				# sidedata.py - Logic around store extra data alongside revlog revisions
				#
				# Copyright 2019 Pierre-Yves David <pierre-yves.david@octobus.net)
				#
				# This software may be used and distributed according to the terms of the
				# GNU General Public License version 2 or any later version.
				"""core code for "sidedata" support

				The "sidedata" are stored alongside the revision without actually being part of
				its content and not affecting its hash. It's main use cases is to cache
				important information related to a changesets.

				The current implementation is experimental and subject to changes. Do not rely
				on it in production.

				Sidedata are stored in the revlog itself, withing the revision rawtext. They
				are inserted, removed from it using the flagprocessors mechanism. The following
				format is currently used::

				initial header:
				<number of sidedata; 2 bytes>
				sidedata (repeated N times):
				<sidedata-key; 2 bytes>
				<sidedata-entry-length: 4 bytes>
				<sidedata-content-sha1-digest: 20 bytes>
				<sidedata-content; X bytes>
				normal raw text:
				<all bytes remaining in the rawtext>

				This is a simple and effective format. It should be enought to experiment with
				the concept.
				"""

				from __future__ import absolute_import