Size: 907
Comment:
|
← Revision 3 as of 2015-07-09 00:07:56 ⇥
Size: 919
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
Line 6: | Line 5: |
Line 11: | Line 9: |
/!\ This is a speculative project and does not represent any firm decisions on future behavior. | /!\ This is a speculative project and does not represent any firm decisions on future behavior. |
Line 16: | Line 14: |
Mercurial have gains multiple new data stored into different file. The fact we use multiple file exposed partial content of transaction at commit time. So we need a new layout for the content of the ``.hg/`` directory. This new layout needs to: |
Mercurial have gains multiple new data stored into different file. The fact we use multiple file exposed partial content of transaction at commit time. So we need a new layout for the content of the .hg/ directory. This new layout needs to: |
Line 21: | Line 18: |
* easily work with the share extensions, | * easily work with the share extensions (see SharedRepository), |
Note:
This page is primarily intended for developers of Mercurial.
Atomic Repository Layout Plan
Status: Project
Main proponents: Pierre-YvesDavid
This is a speculative project and does not represent any firm decisions on future behavior.
Rework the layout of the file in the repository to allow atomic transaction for the new data we have (phase, bookmarks, obsmarkers).
1. Goal
Mercurial have gains multiple new data stored into different file. The fact we use multiple file exposed partial content of transaction at commit time. So we need a new layout for the content of the .hg/ directory. This new layout needs to:
- offer Atomic transaction capabilities,
easily work with the share extensions (see SharedRepository),
- be friendly with cache file,
- provide easier way to compute cache key to detect when the repo changed.