[PATCH] treemanifest: store submanifest revlog per directory
adrian at cadifra.com
Fri May 15 00:52:50 CDT 2015
On 2015-05-15 00:49, Martin von Zweigbergk wrote:
> # HG changeset patch
> # User Martin von Zweigbergk <martinvonz at google.com>
> # Date 1428992462 25200
> # Mon Apr 13 23:21:02 2015 -0700
> # Node ID 01586fff55933fd0eb58e61a123d4c7b03258bd3
> # Parent d1bd0fd07ee6adf4ab3be2b0a0a7c0df54d55abf
> treemanifest: store submanifest revlog per directory
> With this change, when tree manifests are enabled (in .hg/requires),
> commits will be written with one manifest revlog per directory. The
> manifest revlogs are stored in
If this new treemanifest format gets popular in the future, am I right
in assuming that this is intended as the default format in the future?
Or is it intended to remain an optional format forever?
I'm asking this because I think it might be worth investing a bit more
thinking into the layout on disk, especially if the plan is to use
treemanifest per default in the future.
As soon as this new format is engraved in stone, mercurial will
obviously have to live with it until its death.
Note: I'm the author of the current fncache format. And I know what it
means if one has to live with decisions made. For example, when I
created the freaky encoding in store._hashencode, I didn't imagine back
then that someone would ever want to translate that complicated piece
into C. I'm not saying that I would want to (ab)use your layout change
to revisit that decision. I'm just saying that I've 'been there'.
More information about the Mercurial-devel