sidedata: move to new sidedata storage in revlogv2
The current (experimental) sidedata system uses flagprocessors to signify the presence and store/retrieve sidedata from the raw revlog data. This proved to be quite fragile from an exchange perspective and a lot more complex than simply having a dedicated space in the new revlog format. This change does not handle exchange (ironically), so the test for amend - that uses a bundle - is broken. This functionality is split into the next patches. Differential Revision: https://phab.mercurial-scm.org/D9993
Showing
- hgext/lfs/wrapper.py 2 additions, 2 deletionshgext/lfs/wrapper.py
- hgext/remotefilelog/remotefilelog.py 3 additions, 3 deletionshgext/remotefilelog/remotefilelog.py
- mercurial/revlog.py 70 additions, 30 deletionsmercurial/revlog.py
- mercurial/revlogutils/flagutil.py 12 additions, 11 deletionsmercurial/revlogutils/flagutil.py
- mercurial/revlogutils/sidedata.py 13 additions, 27 deletionsmercurial/revlogutils/sidedata.py
- tests/flagprocessorext.py 6 additions, 6 deletionstests/flagprocessorext.py
- tests/simplestorerepo.py 1 addition, 1 deletiontests/simplestorerepo.py
- tests/test-copies-in-changeset.t 7 additions, 5 deletionstests/test-copies-in-changeset.t
- tests/test-revlog-raw.py 3 additions, 3 deletionstests/test-revlog-raw.py
- tests/testlib/ext-sidedata.py 7 additions, 6 deletionstests/testlib/ext-sidedata.py
Loading
Please register or sign in to comment