Differences between revisions 1 and 12 (spanning 11 versions)
Revision 1 as of 2006-12-03 20:34:39
Size: 408
Comment: Describe .hg/requires file
Revision 12 as of 2010-10-10 20:12:21
Size: 914
Editor: abuehl
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Starting with Mercurial version XXX 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`. XXX
 * `foo`
   bar
   The directory `.hg/store` contains the subdirectories `data` (see CaseFoldingPlan)
 * `revlogv1`
   [[RevlogNG]] is used.
 * `fncache`
   store files are named to work around Windows limitations described in [[fncacheRepoFormat]].
 * `dotencode`
   Leading '.' (period) or ' ' (space) in store filenames are encoded (see [[http://selenic.com/repo/hg/rev/34d8247a4595|34d8247a4595]], appears in 1.7).


See also: [[CompatibilityRules]]

----
CategoryInternals

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

  • fncache

    • store files are named to work around Windows limitations described in fncacheRepoFormat.

  • dotencode

    • Leading '.' (period) or ' ' (space) in store filenames are encoded (see 34d8247a4595, appears in 1.7).

See also: CompatibilityRules


CategoryInternals

RequiresFile (last edited 2013-09-13 22:34:47 by mpm)