Page MenuHomePhabricator

nodemap: track the maximum revision tracked in the nodemap
ClosedPublic

Authored by marmoute on Jan 15 2020, 9:55 AM.

Details

Summary

We need a simple way to detect when the on disk data contains less revision
than the index we read from disk. The docket file is meant for this, we just had
to start tracking that data.

We should also try to detect strip operation, but we will deal with this in
later changesets. Right now we are focusing on defining the API for index
supporting persistent nodemap.

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

marmoute created this revision.Jan 15 2020, 9:55 AM
marmoute updated this revision to Diff 19433.Jan 17 2020, 1:07 PM
marmoute updated this revision to Diff 19769.Fri, Jan 31, 10:29 AM
marmoute updated this revision to Diff 19796.Fri, Jan 31, 6:00 PM
marmoute updated this revision to Diff 19840.Sun, Feb 2, 3:19 AM

small doc update on .#s[1]

marmoute updated this revision to Diff 19900.Tue, Feb 4, 7:25 PM

rebase to latest default

This revision was not accepted when it landed; it landed in state Needs Review.
This revision was automatically updated to reflect the committed changes.