##// END OF EJS Templates
sidedata-exchange: rewrite sidedata on-the-fly whenever possible...
sidedata-exchange: rewrite sidedata on-the-fly whenever possible When a A exchanges with B, the difference of their supported sidedata categories is made, and the responsibility is always with the client to generated it: - If A pushes to B and B requires category `foo` that A does not have, A will need to generate it when sending it to B. - If A pulls from B and A needs category `foo`, it will generate `foo` before the end of the transaction. - Any category that is not required is removed. If peers are not compatible, abort. It is forbidden to rewrite sidedata for a rev that already has sidedata, since that would introduce unreachable (garbage) data in the data file, something we're not prepared for yet. Differential Revision: https://phab.mercurial-scm.org/D10032

File last commit:

r45036:fdc802f2 default
r47452:ba8e508a default
Show More
ext-phase-report.py
31 lines | 1.0 KiB | text/x-python | PythonLexer
# tiny extension to report phase changes during transaction
from __future__ import absolute_import
def reposetup(ui, repo):
def reportphasemove(tr):
for revs, move in sorted(tr.changes[b"phases"], key=lambda r: r[0][0]):
for rev in revs:
if move[0] is None:
ui.write(
(
b'test-debug-phase: new rev %d: x -> %d\n'
% (rev, move[1])
)
)
else:
ui.write(
(
b'test-debug-phase: move rev %d: %d -> %d\n'
% (rev, move[0], move[1])
)
)
class reportphaserepo(repo.__class__):
def transaction(self, *args, **kwargs):
tr = super(reportphaserepo, self).transaction(*args, **kwargs)
tr.addpostclose(b'report-phase', reportphasemove)
return tr
repo.__class__ = reportphaserepo