|
Size: 470
Comment:
|
Size: 567
Comment: simpler RevlogNG link, clarification for parameters.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Starting with Mercurial version 0.9.2 there is a file `.hg/requires` which specifies the capabilities needed by a client to access this repository. It is a text file, where each line contains the name of a capability and optionally a parameter separated by a `=` character. | Starting with Mercurial version 0.9.2 there is a file `.hg/requires` which specifies the capabilities needed by a client to access this repository. It is a text file, where each line contains the name of a capability and optionally (separated by a `=` character from the name) a list of parameters, each separated by a comma (`,`). Currently there are only capabilities which don't need parameters. |
| Line 6: | Line 8: |
| The directory `.hg/store` contains the subdirectories `data` and `meta`, ... (see CaseFoldingPlan) | The directory `.hg/store` contains the subdirectories `data` (see CaseFoldingPlan) |
| Line 8: | Line 10: |
| RevlogNG is used. (see ["RevlogNG"]) | ["RevlogNG"] is used. |
Starting with Mercurial version 0.9.2 there is a file .hg/requires which specifies the capabilities needed by a client to access this repository. It is a text file, where each line contains the name of a capability and optionally (separated by a = character from the name) a list of parameters, each separated by a comma (,).
Currently there are only capabilities which don't need parameters.
Capabilities
store
The directory .hg/store contains the subdirectories data (see CaseFoldingPlan)
revlogv1
- ["RevlogNG"] is used.