Not sure what "inmem" was supposed to indicate. This object is an
interface to manifest data on disk as well as "in memory" (assuming
that's what "inmem" means).
Details
Details
- Reviewers
 - None
 - Group Reviewers
 hg-reviewers - Commits
 - rHG071f97d03acb: manifest: rename manifestlog._treeinmem to ._treemanifests
 
Diff Detail
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
| mercurial/manifest.py | ||
|---|---|---|
| 1275 | _treeinmem was used for indicating that the treemanifest type should be used in memory and this variable (_treeondisk) was used for indicating that treemanifest revlogs should be used. The only reason this distinction was useful was so you could set manually force _treeinmem = True in the code and run the test suite to make sure that the treemanifest type worked.  | |
_treeinmem was used for indicating that the treemanifest type should be used in memory and this variable (_treeondisk) was used for indicating that treemanifest revlogs should be used. The only reason this distinction was useful was so you could set manually force _treeinmem = True in the code and run the test suite to make sure that the treemanifest type worked.