comparison mercurial/helptext/internals/requirements.txt @ 44841:526d69eeea31

upgrade: support upgrade and downgrade from persistent nodemap The requirements is now recognised and dealt with and the associated files properly handled. The persistent nodemap should be ready for usage in the field now. Differential Revision: https://phab.mercurial-scm.org/D8431
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Tue, 14 Apr 2020 06:09:14 +0200
parents 2e017696181f
children 63eb1b5c580d
comparison
equal deleted inserted replaced
44840:4ba2a6ffcf24 44841:526d69eeea31
140 140
141 Support for this requirement was added in Mercurial 5.1 (released 141 Support for this requirement was added in Mercurial 5.1 (released
142 August 2019). The requirement will only be present on repositories 142 August 2019). The requirement will only be present on repositories
143 that have opted in to this format (by having 143 that have opted in to this format (by having
144 ``format.bookmarks-in-store=true`` set when they were created). 144 ``format.bookmarks-in-store=true`` set when they were created).
145
146 persistent-nodemap
147 ==================
148
149 The `nodemap` index (mapping nodeid to local revision number) is persisted on
150 disk. This provides speed benefit (if the associated native code is used). The
151 persistent nodemap is only used for two revlogs: the changelog and the
152 manifestlog.
153
154 Support for this requirement was added in Mercurial 5.5 (released August 2020).
155 Note that as of 5.5, only installations compiled with the Rust extension will
156 benefit from a speedup. The other installations will do the necessary work to
157 keep the index up to date, but will suffer a slowdown.