dirstate-v2: fix confusion between requirement and format config variable

None of those outputs failed on the CI because dirstate-v2 is not fully tested
yet. This also updates the documentation.

Differential Revision: https://phab.mercurial-scm.org/D11746

mercurial/helptext/internals/dirstate-v2.txt

@@ -1,616 +1,616 b''
 The *dirstate* is what Mercurial uses internally to track
 the state of files in the working directory,
 such as set by commands like `hg add` and `hg rm`.
 It also contains some cached data that help make `hg status` faster.
 The name refers both to `.hg/dirstate` on the filesystem
 and the corresponding data structure in memory while a Mercurial process
 is running.
 
 The original file format, retroactively dubbed `dirstate-v1`,
 is described at https://www.mercurial-scm.org/wiki/DirState.
 It is made of a flat sequence of unordered variable-size entries,
 so accessing any information in it requires parsing all of it.
 Similarly, saving changes requires rewriting the entire file.
 
 The newer `dirsate-v2` file format is designed to fix these limitations
 and make `hg status` faster.
 
 User guide
 ==========
 
 Compatibility
 -------------
 
 The file format is experimental and may still change.
 Different versions of Mercurial may not be compatible with each other
 when working on a local repository that uses this format.
 When using an incompatible version with the experimental format,
 anything can happen including data corruption.
 
 Since the dirstate is entirely local and not relevant to the wire protocol,
 `dirstate-v2` does not affect compatibility with remote Mercurial versions.
 
 When `share-safe` is enabled, different repositories sharing the same store
 can use different dirstate formats.
 
 Enabling `dirsate-v2` for new local repositories
 ------------------------------------------------
 
 When creating a new local repository such as with `hg init` or `hg clone`,
 the `exp-rc-dirstate-v2` boolean in the `format` configuration section
 controls whether to use this file format.
 This is disabled by default as of this writing.
 To enable it for a single repository, run for example::
 
     $ hg init my-project --config format.exp-rc-dirstate-v2=1
 
 Checking the format of an existing local repsitory
 --------------------------------------------------
 
 The `debugformat` commands prints information about
 which of multiple optional formats are used in the current repository,
 including `dirstate-v2`::
 
     $ hg debugformat
     format-variant     repo
     fncache:            yes
     dirstate-v2:        yes
     […]
 
 Upgrading or downgrading an existing local repository
 -----------------------------------------------------
 
 The `debugupgrade` command does various upgrades or downgrades
 on a local repository
 based on the current Mercurial version and on configuration.
 The same `format.exp-rc-dirstate-v2` configuration is used again.
 
 Example to upgrade::
 
     $ hg debugupgrade --config format.exp-rc-dirstate-v2=1
 
 Example to downgrade to `dirstate-v1`::
 
     $ hg debugupgrade --config format.exp-rc-dirstate-v2=0
 
 Both of this commands do nothing but print a list of proposed changes,
 which may include changes unrelated to the dirstate.
 Those other changes are controlled by their own configuration keys.
 Add `--run` to a command to actually apply the proposed changes.
 
 Backups of `.hg/requires` and `.hg/dirstate` are created
 in a `.hg/upgradebackup.*` directory.
 If something goes wrong, restoring those files should undo the change.
 
 Note that upgrading affects compatibility with older versions of Mercurial
 as noted above.
 This can be relevant when a repository’s files are on a USB drive
 or some other removable media, or shared over the network, etc.
 
 Internal filesystem representation
 ==================================
 
 Requirements file
 -----------------
 
 The `.hg/requires` file indicates which of various optional file formats
 are used by a given repository.
 Mercurial aborts when seeing a requirement it does not know about,
 which avoids older version accidentally messing up a respository
 that uses a format that was introduced later.
 For versions that do support a format, the presence or absence of
 the corresponding requirement indicates whether to use that format.
 
-When the file contains a `exp-dirstate-v2` line,
+When the file contains a `dirstate-v2` line,
 the `dirstate-v2` format is used.
 With no such line `dirstate-v1` is used.
 
 High level description
 ----------------------
 
 Whereas `dirstate-v1` uses a single `.hg/disrtate` file,
 in `dirstate-v2` that file is a "docket" file
 that only contains some metadata
 and points to separate data file named `.hg/dirstate.{ID}`,
 where `{ID}` is a random identifier.
 
 This separation allows making data files append-only
 and therefore safer to memory-map.
 Creating a new data file (occasionally to clean up unused data)
 can be done with a different ID
 without disrupting another Mercurial process
 that could still be using the previous data file.
 
 Both files have a format designed to reduce the need for parsing,
 by using fixed-size binary components as much as possible.
 For data that is not fixed-size,
 references to other parts of a file can be made by storing "pseudo-pointers":
 integers counted in bytes from the start of a file.
 For read-only access no data structure is needed,
 only a bytes buffer (possibly memory-mapped directly from the filesystem)
 with specific parts read on demand.
 
 The data file contains "nodes" organized in a tree.
 Each node represents a file or directory inside the working directory
 or its parent changeset.
 This tree has the same structure as the filesystem,
 so a node representing a directory has child nodes representing
 the files and subdirectories contained directly in that directory.
 
 The docket file format
 ----------------------
 
 This is implemented in `rust/hg-core/src/dirstate_tree/on_disk.rs`
 and `mercurial/dirstateutils/docket.py`.
 
 Components of the docket file are found at fixed offsets,
 counted in bytes from the start of the file:
 
 * Offset 0:
   The 12-bytes marker string "dirstate-v2\n" ending with a newline character.
   This makes it easier to tell a dirstate-v2 file from a dirstate-v1 file,
   although it is not strictly necessary
   since `.hg/requires` determines which format to use.
 
 * Offset 12:
   The changeset node ID on the first parent of the working directory,
   as up to 32 binary bytes.
   If a node ID is shorter (20 bytes for SHA-1),
   it is start-aligned and the rest of the bytes are set to zero.
 
 * Offset 44:
   The changeset node ID on the second parent of the working directory,
   or all zeros if there isn’t one.
   Also 32 binary bytes.
 
 * Offset 76:
   Tree metadata on 44 bytes, described below.
   Its separation in this documentation from the rest of the docket
   reflects a detail of the current implementation.
   Since tree metadata is also made of fields at fixed offsets, those could
   be inlined here by adding 76 bytes to each offset.
 
 * Offset 120:
   The used size of the data file, as a 32-bit big-endian integer.
   The actual size of the data file may be larger
   (if another Mercurial processis in appending to it
   but has not updated the docket yet).
   That extra data must be ignored.
 
 * Offset 124:
   The length of the data file identifier, as a 8-bit integer.
 
 * Offset 125:
   The data file identifier.
 
 * Any additional data is current ignored, and dropped when updating the file.
 
 Tree metadata in the docket file
 --------------------------------
 
 Tree metadata is similarly made of components at fixed offsets.
 These offsets are counted in bytes from the start of tree metadata,
 which is 76 bytes after the start of the docket file.
 
 This metadata can be thought of as the singular root of the tree
 formed by nodes in the data file.
 
 * Offset 0:
   Pseudo-pointer to the start of root nodes,
   counted in bytes from the start of the data file,
   as a 32-bit big-endian integer.
   These nodes describe files and directories found directly
   at the root of the working directory.
 
 * Offset 4:
   Number of root nodes, as a 32-bit big-endian integer.
 
 * Offset 8:
   Total number of nodes in the entire tree that "have a dirstate entry",
   as a 32-bit big-endian integer.
   Those nodes represent files that would be present at all in `dirstate-v1`.
   This is typically less than the total number of nodes.
   This counter is used to implement `len(dirstatemap)`.
 
 * Offset 12:
   Number of nodes in the entire tree that have a copy source,
   as a 32-bit big-endian integer.
   At the next commit, these files are recorded
   as having been copied or moved/renamed from that source.
   (A move is recorded as a copy and separate removal of the source.)
   This counter is used to implement `len(dirstatemap.copymap)`.
 
 * Offset 16:
   An estimation of how many bytes of the data file
   (within its used size) are unused, as a 32-bit big-endian integer.
   When appending to an existing data file,
   some existing nodes or paths can be unreachable from the new root
   but they still take up space.
   This counter is used to decide when to write a new data file from scratch
   instead of appending to an existing one,
   in order to get rid of that unreachable data
   and avoid unbounded file size growth.
 
 * Offset 20:
   These four bytes are currently ignored
   and reset to zero when updating a docket file.
   This is an attempt at forward compatibility:
   future Mercurial versions could use this as a bit field
   to indicate that a dirstate has additional data or constraints.
   Finding a dirstate file with the relevant bit unset indicates that
   it was written by a then-older version
   which is not aware of that future change.
 
 * Offset 24:
   Either 20 zero bytes, or a SHA-1 hash as 20 binary bytes.
   When present, the hash is of ignore patterns
   that were used for some previous run of the `status` algorithm.
 
 * (Offset 44: end of tree metadata)
 
 Optional hash of ignore patterns
 --------------------------------
 
 The implementation of `status` at `rust/hg-core/src/dirstate_tree/status.rs`
 has been optimized such that its run time is dominated by calls
 to `stat` for reading the filesystem metadata of a file or directory,
 and to `readdir` for listing the contents of a directory.
 In some cases the algorithm can skip calls to `readdir`
 (saving significant time)
 because the dirstate already contains enough of the relevant information
 to build the correct `status` results.
 
 The default configuration of `hg status` is to list unknown files
 but not ignored files.
 In this case, it matters for the `readdir`-skipping optimization
 if a given file used to be ignored but became unknown
 because `.hgignore` changed.
 To detect the possibility of such a change,
 the tree metadata contains an optional hash of all ignore patterns.
 
 We define:
 
 * "Root" ignore files as:
 
   - `.hgignore` at the root of the repository if it exists
   - And all files from `ui.ignore.*` config.
 
   This set of files is sorted by the string representation of their path.
 
 * The "expanded contents" of an ignore files is the byte string made
   by the concatenation of its contents followed by the "expanded contents"
   of other files included with `include:` or `subinclude:` directives,
   in inclusion order. This definition is recursive, as included files can
   themselves include more files.
 
 This hash is defined as the SHA-1 of the concatenation (in sorted
 order) of the "expanded contents" of each "root" ignore file.
 (Note that computing this does not require actually concatenating
 into a single contiguous byte sequence.
 Instead a SHA-1 hasher object can be created
 and fed separate chunks one by one.)
 
 The data file format
 --------------------
 
 This is implemented in `rust/hg-core/src/dirstate_tree/on_disk.rs`
 and `mercurial/dirstateutils/v2.py`.
 
 The data file contains two types of data: paths and nodes.
 
 Paths and nodes can be organized in any order in the file, except that sibling
 nodes must be next to each other and sorted by their path.
 Contiguity lets the parent refer to them all
 by their count and a single pseudo-pointer,
 instead of storing one pseudo-pointer per child node.
 Sorting allows using binary seach to find a child node with a given name
 in `O(log(n))` byte sequence comparisons.
 
 The current implemention writes paths and child node before a given node
 for ease of figuring out the value of pseudo-pointers by the time the are to be
 written, but this is not an obligation and readers must not rely on it.
 
 A path is stored as a byte string anywhere in the file, without delimiter.
 It is refered to by one or more node by a pseudo-pointer to its start, and its
 length in bytes. Since there is no delimiter,
 when a path is a substring of another the same bytes could be reused,
 although the implementation does not exploit this as of this writing.
 
 A node is stored on 43 bytes with components at fixed offsets. Paths and
 child nodes relevant to a node are stored externally and referenced though
 pseudo-pointers.
 
 All integers are stored in big-endian. All pseudo-pointers are 32-bit integers
 counting bytes from the start of the data file. Path lengths and positions
 are 16-bit integers, also counted in bytes.
 
 Node components are:
 
 * Offset 0:
   Pseudo-pointer to the full path of this node,
   from the working directory root.
 
 * Offset 4:
   Length of the full path.
 
 * Offset 6:
   Position of the last `/` path separator within the full path,
   in bytes from the start of the full path,
   or zero if there isn’t one.
   The part of the full path after this position is the "base name".
   Since sibling nodes have the same parent, only their base name vary
   and needs to be considered when doing binary search to find a given path.
 
 * Offset 8:
   Pseudo-pointer to the "copy source" path for this node,
   or zero if there is no copy source.
 
 * Offset 12:
   Length of the copy source path, or zero if there isn’t one.
 
 * Offset 14:
   Pseudo-pointer to the start of child nodes.
 
 * Offset 18:
   Number of child nodes, as a 32-bit integer.
   They occupy 43 times this number of bytes
   (not counting space for paths, and further descendants).
 
 * Offset 22:
   Number as a 32-bit integer of descendant nodes in this subtree,
   not including this node itself,
   that "have a dirstate entry".
   Those nodes represent files that would be present at all in `dirstate-v1`.
   This is typically less than the total number of descendants.
   This counter is used to implement `has_dir`.
 
 * Offset 26:
   Number as a 32-bit integer of descendant nodes in this subtree,
   not including this node itself,
   that represent files tracked in the working directory.
   (For example, `hg rm` makes a file untracked.)
   This counter is used to implement `has_tracked_dir`.
 
 * Offset 30:
   A `flags` fields  that packs some boolean values as bits of a 16-bit integer.
   Starting from least-significant, bit masks are::
 
     WDIR_TRACKED = 1 << 0
     P1_TRACKED = 1 << 1
     P2_INFO = 1 << 2
     MODE_EXEC_PERM = 1 << 3
     MODE_IS_SYMLINK = 1 << 4
     HAS_FALLBACK_EXEC = 1 << 5
     FALLBACK_EXEC = 1 << 6
     HAS_FALLBACK_SYMLINK = 1 << 7
     FALLBACK_SYMLINK = 1 << 8
     EXPECTED_STATE_IS_MODIFIED = 1 << 9
     HAS_MODE_AND_SIZE = 1 << 10
     HAS_MTIME = 1 << 11
     MTIME_SECOND_AMBIGUOUS = 1 << 12
     DIRECTORY = 1 << 13
     ALL_UNKNOWN_RECORDED = 1 << 14
     ALL_IGNORED_RECORDED = 1 << 15
 
   The meaning of each bit is described below.
 
   Other bits are unset.
   They may be assigned meaning if the future,
   with the limitation that Mercurial versions that pre-date such meaning
   will always reset those bits to unset when writing nodes.
   (A new node is written for any mutation in its subtree,
   leaving the bytes of the old node unreachable
   until the data file is rewritten entirely.)
 
 * Offset 32:
   A `size` field described below, as a 32-bit integer.
   Unlike in dirstate-v1, negative values are not used.
 
 * Offset 36:
   The seconds component of an `mtime` field described below,
   as a 32-bit integer.
   Unlike in dirstate-v1, negative values are not used.
   When `mtime` is used, this is number of seconds since the Unix epoch
   truncated to its lower 31 bits.
 
 * Offset 40:
   The nanoseconds component of an `mtime` field described below,
   as a 32-bit integer.
   When `mtime` is used,
   this is the number of nanoseconds since `mtime.seconds`,
   always stritctly less than one billion.
 
   This may be zero if more precision is not available.
   (This can happen because of limitations in any of Mercurial, Python,
   libc, the operating system, …)
 
   When comparing two mtimes and either has this component set to zero,
   the sub-second precision of both should be ignored.
   False positives when checking mtime equality due to clock resolution
   are always possible and the status algorithm needs to deal with them,
   but having too many false negatives could be harmful too.
 
 * (Offset 44: end of this node)
 
 The meaning of the boolean values packed in `flags` is:
 
 `WDIR_TRACKED`
     Set if the working directory contains a tracked file at this node’s path.
     This is typically set and unset by `hg add` and `hg rm`.
 
 `P1_TRACKED`
     Set if the working directory’s first parent changeset
     (whose node identifier is found in tree metadata)
     contains a tracked file at this node’s path.
     This is a cache to reduce manifest lookups.
 
 `P2_INFO`
     Set if the file has been involved in some merge operation.
     Either because it was actually merged,
     or because the version in the second parent p2 version was ahead,
     or because some rename moved it there.
     In either case `hg status` will want it displayed as modified.
 
 Files that would be mentioned at all in the `dirstate-v1` file format
 have a node with at least one of the above three bits set in `dirstate-v2`.
 Let’s call these files "tracked anywhere",
 and "untracked" the nodes with all three of these bits unset.
 Untracked nodes are typically for directories:
 they hold child nodes and form the tree structure.
 Additional untracked nodes may also exist.
 Although implementations should strive to clean up nodes
 that are entirely unused, other untracked nodes may also exist.
 For example, a future version of Mercurial might in some cases
 add nodes for untracked files or/and ignored files in the working directory
 in order to optimize `hg status`
 by enabling it to skip `readdir` in more cases.
 
 `HAS_MODE_AND_SIZE`
     Must be unset for untracked nodes.
     For files tracked anywhere, if this is set:
     - The `size` field is the expected file size,
       in bytes truncated its lower to 31 bits.
     - The expected execute permission for the file’s owner
       is given by `MODE_EXEC_PERM`
     - The expected file type is given by `MODE_IS_SIMLINK`:
       a symbolic link if set, or a normal file if unset.
     If this is unset the expected size, permission, and file type are unknown.
     The `size` field is unused (set to zero).
 
 `HAS_MTIME`
     The nodes contains a "valid" last modification time in the `mtime` field.
 
 
     It means the `mtime` was already strictly in the past when observed,
     meaning that later changes cannot happen in the same clock tick
     and must cause a different modification time
     (unless the system clock jumps back and we get unlucky,
     which is not impossible but deemed unlikely enough).
 
     This means that if `std::fs::symlink_metadata` later reports
     the same modification time
     and ignored patterns haven’t changed,
     we can assume the node to be unchanged on disk.
 
     The `mtime` field can then be used to skip more expensive lookup when
     checking the status of "tracked" nodes.
 
     It can also be set for node where `DIRECTORY` is set.
     See `DIRECTORY` documentation for details.
 
 `DIRECTORY`
     When set, this entry will match a directory that exists or existed on the
     file system.
 
     * When `HAS_MTIME` is set a directory has been seen on the file system and
       `mtime` matches its last modificiation time. However, `HAS_MTIME` not being set
       does not indicate the lack of directory on the file system.
 
     * When not tracked anywhere, this node does not represent an ignored or
       unknown file on disk.
 
     If `HAS_MTIME` is set
     and `mtime` matches the last modification time of the directory on disk,
     the directory is unchanged
     and we can skip calling `std::fs::read_dir` again for this directory,
     and iterate child dirstate nodes instead.
     (as long as `ALL_UNKNOWN_RECORDED` and `ALL_IGNORED_RECORDED` are taken
     into account)
 
 `MODE_EXEC_PERM`
     Must be unset if `HAS_MODE_AND_SIZE` is unset.
     If `HAS_MODE_AND_SIZE` is set,
     this indicates whether the file’s own is expected
     to have execute permission.
 
     Beware that on system without fs support for this information, the value
     stored in the dirstate might be wrong and should not be relied on.
 
 `MODE_IS_SYMLINK`
     Must be unset if `HAS_MODE_AND_SIZE` is unset.
     If `HAS_MODE_AND_SIZE` is set,
     this indicates whether the file is expected to be a symlink
     as opposed to a normal file.
 
     Beware that on system without fs support for this information, the value
     stored in the dirstate might be wrong and should not be relied on.
 
 `EXPECTED_STATE_IS_MODIFIED`
     Must be unset for untracked nodes.
     For:
     - a file tracked anywhere
     - that has expected metadata (`HAS_MODE_AND_SIZE` and `HAS_MTIME`)
     - if that metadata matches
       metadata found in the working directory with `stat`
     This bit indicates the status of the file.
     If set, the status is modified. If unset, it is clean.
 
     In cases where `hg status` needs to read the contents of a file
     because metadata is ambiguous, this bit lets it record the result
     if the result is modified so that a future run of `hg status`
     does not need to do the same again.
     It is valid to never set this bit,
     and consider expected metadata ambiguous if it is set.
 
 `ALL_UNKNOWN_RECORDED`
     If set, all "unknown" children existing on disk (at the time of the last
     status) have been recorded and the `mtime` associated with
     `DIRECTORY` can be used for optimization even when "unknown" file
     are listed.
 
     Note that the amount recorded "unknown" children can still be zero if None
     where present.
 
     Also note that having this flag unset does not imply that no "unknown"
     children have been recorded. Some might be present, but there is no garantee
     that is will be all of them.
 
 `ALL_IGNORED_RECORDED`
     If set, all "ignored" children existing on disk (at the time of the last
     status) have been recorded and the `mtime` associated with
     `DIRECTORY` can be used for optimization even when "ignored" file
     are listed.
 
     Note that the amount recorded "ignored" children can still be zero if None
     where present.
 
     Also note that having this flag unset does not imply that no "ignored"
     children have been recorded. Some might be present, but there is no garantee
     that is will be all of them.
 
 `HAS_FALLBACK_EXEC`
     If this flag is set, the entry carries "fallback" information for the
     executable bit in the `FALLBACK_EXEC` flag.
 
     Fallback information can be stored in the dirstate to keep track of
     filesystem attribute tracked by Mercurial when the underlying file
     system or operating system does not support that property, (e.g.
     Windows).
 
 `FALLBACK_EXEC`
     Should be ignored if `HAS_FALLBACK_EXEC` is unset. If set the file for this
     entry should be considered executable if that information cannot be
     extracted from the file system. If unset it should be considered
     non-executable instead.
 
 `HAS_FALLBACK_SYMLINK`
     If this flag is set, the entry carries "fallback" information for symbolic
     link status in the `FALLBACK_SYMLINK` flag.
 
     Fallback information can be stored in the dirstate to keep track of
     filesystem attribute tracked by Mercurial when the underlying file
     system or operating system does not support that property, (e.g.
     Windows).
 
 `FALLBACK_SYMLINK`
     Should be ignored if `HAS_FALLBACK_SYMLINK` is unset. If set the file for
     this entry should be considered a symlink if that information cannot be
     extracted from the file system. If unset it should be considered a normal
     file instead.
 
 `MTIME_SECOND_AMBIGUOUS`
     This flag is relevant only when `HAS_FILE_MTIME` is set.  When set, the
     `mtime` stored in the entry is only valid for comparison with timestamps
     that have nanosecond information. If available timestamp does not carries
     nanosecond information, the `mtime` should be ignored and no optimisation
     can be applied.

tests/test-init.t

@@ -1,316 +1,316 b''
 This test tries to exercise the ssh functionality with a dummy script
 
   $ checknewrepo()
   > {
   >    name=$1
   >    if [ -d "$name"/.hg/store ]; then
   >    echo store created
   >    fi
   >    if [ -f "$name"/.hg/00changelog.i ]; then
   >    echo 00changelog.i created
   >    fi
   >    cat "$name"/.hg/requires
   > }
 
 creating 'local'
 
   $ hg init local
   $ checknewrepo local
   store created
   00changelog.i created
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
   $ echo this > local/foo
   $ hg ci --cwd local -A -m "init"
   adding foo
 
 test custom revlog chunk cache sizes
 
   $ hg --config format.chunkcachesize=0 log -R local -pv
   abort: revlog chunk cache size 0 is not greater than 0
   [50]
   $ hg --config format.chunkcachesize=1023 log -R local -pv
   abort: revlog chunk cache size 1023 is not a power of 2
   [50]
   $ hg --config format.chunkcachesize=1024 log -R local -pv
   changeset:   0:08b9e9f63b32
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files:       foo
   description:
   init
   
   
   diff -r 000000000000 -r 08b9e9f63b32 foo
   --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
   +++ b/foo	Thu Jan 01 00:00:00 1970 +0000
   @@ -0,0 +1,1 @@
   +this
   
 
 creating repo with format.usestore=false
 
   $ hg --config format.usestore=false init old
   $ checknewrepo old
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   testonly-simplestore (reposimplestore !)
   sparserevlog
 
 creating repo with format.usefncache=false
 
   $ hg --config format.usefncache=false init old2
   $ checknewrepo old2
   store created
   00changelog.i created
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 creating repo with format.dotencode=false
 
   $ hg --config format.dotencode=false init old3
   $ checknewrepo old3
   store created
   00changelog.i created
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 creating repo with format.dotencode=false
 
   $ hg --config format.generaldelta=false --config format.usegeneraldelta=false --config format.sparse-revlog=no init old4
   $ checknewrepo old4
   store created
   00changelog.i created
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   store
   testonly-simplestore (reposimplestore !)
 
 test failure
 
   $ hg init local
   abort: repository local already exists
   [255]
 
 init+push to remote2
 
   $ hg init ssh://user@dummy/remote2
   $ hg incoming -R remote2 local
   comparing with local
   changeset:   0:08b9e9f63b32
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     init
   
 
   $ hg push -R local ssh://user@dummy/remote2
   pushing to ssh://user@dummy/remote2
   searching for changes
   remote: adding changesets
   remote: adding manifests
   remote: adding file changes
   remote: added 1 changesets with 1 changes to 1 files
 
 clone to remote1
 
   $ hg clone local ssh://user@dummy/remote1
   searching for changes
   remote: adding changesets
   remote: adding manifests
   remote: adding file changes
   remote: added 1 changesets with 1 changes to 1 files
 
 The largefiles extension doesn't crash
   $ hg clone local ssh://user@dummy/remotelf --config extensions.largefiles=
   The fsmonitor extension is incompatible with the largefiles extension and has been disabled. (fsmonitor !)
   The fsmonitor extension is incompatible with the largefiles extension and has been disabled. (fsmonitor !)
   searching for changes
   remote: adding changesets
   remote: adding manifests
   remote: adding file changes
   remote: added 1 changesets with 1 changes to 1 files
 
 init to existing repo
 
   $ hg init ssh://user@dummy/remote1
   abort: repository remote1 already exists
   abort: could not create remote repo
   [255]
 
 clone to existing repo
 
   $ hg clone local ssh://user@dummy/remote1
   abort: repository remote1 already exists
   abort: could not create remote repo
   [255]
 
 output of dummyssh
 
   $ cat dummylog
   Got arguments 1:user@dummy 2:hg init remote2
   Got arguments 1:user@dummy 2:hg -R remote2 serve --stdio
   Got arguments 1:user@dummy 2:hg -R remote2 serve --stdio
   Got arguments 1:user@dummy 2:hg init remote1
   Got arguments 1:user@dummy 2:hg -R remote1 serve --stdio
   Got arguments 1:user@dummy 2:hg init remotelf
   Got arguments 1:user@dummy 2:hg -R remotelf serve --stdio
   Got arguments 1:user@dummy 2:hg init remote1
   Got arguments 1:user@dummy 2:hg init remote1
 
 comparing repositories
 
   $ hg tip -q -R local
   0:08b9e9f63b32
   $ hg tip -q -R remote1
   0:08b9e9f63b32
   $ hg tip -q -R remote2
   0:08b9e9f63b32
 
 check names for repositories (clashes with URL schemes, special chars)
 
   $ for i in bundle file hg http https old-http ssh static-http "with space"; do
   >   printf "hg init \"$i\"... "
   >   hg init "$i"
   >   test -d "$i" -a -d "$i/.hg" && echo "ok" || echo "failed"
   > done
   hg init "bundle"... ok
   hg init "file"... ok
   hg init "hg"... ok
   hg init "http"... ok
   hg init "https"... ok
   hg init "old-http"... ok
   hg init "ssh"... ok
   hg init "static-http"... ok
   hg init "with space"... ok
 #if eol-in-paths
 /* " " is not a valid name for a directory on Windows */
   $ hg init " "
   $ test -d " "
   $ test -d " /.hg"
 #endif
 
 creating 'local/sub/repo'
 
   $ hg init local/sub/repo
   $ checknewrepo local/sub/repo
   store created
   00changelog.i created
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 prepare test of init of url configured from paths
 
   $ echo '[paths]' >> $HGRCPATH
   $ echo "somewhere = `pwd`/url from paths" >> $HGRCPATH
   $ echo "elsewhere = `pwd`/another paths url" >> $HGRCPATH
 
 init should (for consistency with clone) expand the url
 
   $ hg init somewhere
   $ checknewrepo "url from paths"
   store created
   00changelog.i created
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 verify that clone also expand urls
 
   $ hg clone somewhere elsewhere
   updating to branch default
   0 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ checknewrepo "another paths url"
   store created
   00changelog.i created
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 clone bookmarks
 
   $ hg -R local bookmark test
   $ hg -R local bookmarks
    * test                      0:08b9e9f63b32
   $ hg clone local ssh://user@dummy/remote-bookmarks
   searching for changes
   remote: adding changesets
   remote: adding manifests
   remote: adding file changes
   remote: added 1 changesets with 1 changes to 1 files
   exporting bookmark test
   $ hg -R remote-bookmarks bookmarks
      test                      0:08b9e9f63b32
 
 Check format constraint
 -----------------------
 
   $ hg init issue6056 --config format.usegeneraldelta=0 --config format.sparse-revlog=0
   $ cd issue6056
   $ echo foo > 1
   $ echo foo > 2
   $ echo foo > 3
   $ echo foo > 4
   $ echo foo > 5
   $ hg add *
 
 Build a bogus repository (sparserevlog without general delta)
 
   $ hg commit -m 'initial changesets'
   $ echo 'sparserevlog' >> .hg/requires
   $ for x in `$TESTDIR/seq.py 100`; do
   >     echo $x >> `expr $x % 5 + 1`
   >     hg commit -m $x
   > done
   $ cd ..

tests/test-lfconvert.t

@@ -1,411 +1,411 b''
   $ USERCACHE="$TESTTMP/cache"; export USERCACHE
   $ mkdir "${USERCACHE}"
   $ cat >> $HGRCPATH <<EOF
   > [extensions]
   > largefiles =
   > share =
   > strip =
   > convert =
   > [largefiles]
   > minsize = 0.5
   > patterns = **.other
   >     **.dat
   > usercache=${USERCACHE}
   > EOF
 
 "lfconvert" works
   $ hg init bigfile-repo
   $ cd bigfile-repo
   $ cat >> .hg/hgrc <<EOF
   > [extensions]
   > largefiles = !
   > EOF
   $ mkdir sub
   $ dd if=/dev/zero bs=1k count=256 > large 2> /dev/null
   $ dd if=/dev/zero bs=1k count=256 > large2 2> /dev/null
   $ echo normal > normal1
   $ echo alsonormal > sub/normal2
   $ dd if=/dev/zero bs=1k count=10 > sub/maybelarge.dat 2> /dev/null
   $ hg addremove
   adding large
   adding large2
   adding normal1
   adding sub/maybelarge.dat
   adding sub/normal2
   $ hg commit -m"add large, normal1" large normal1
   $ hg commit -m"add sub/*" sub
 
 Test tag parsing
   $ cat >> .hgtags <<EOF
   > IncorrectlyFormattedTag!
   > invalidhash sometag
   > 0123456789abcdef anothertag
   > EOF
   $ hg add .hgtags
   $ hg commit -m"add large2" large2 .hgtags
 
 Test link+rename largefile codepath
   $ [ -d .hg/largefiles ] && echo fail || echo pass
   pass
   $ cd ..
   $ hg lfconvert --size 0.2 bigfile-repo largefiles-repo
   initializing destination largefiles-repo
   skipping incorrectly formatted tag IncorrectlyFormattedTag!
   skipping incorrectly formatted id invalidhash
   no mapping for id 0123456789abcdef
 #if symlink
   $ hg --cwd bigfile-repo rename large2 large3
   $ ln -sf large bigfile-repo/large3
   $ hg --cwd bigfile-repo commit -m"make large2 a symlink" large2 large3
   $ hg lfconvert --size 0.2 bigfile-repo largefiles-repo-symlink
   initializing destination largefiles-repo-symlink
   skipping incorrectly formatted tag IncorrectlyFormattedTag!
   skipping incorrectly formatted id invalidhash
   no mapping for id 0123456789abcdef
   abort: renamed/copied largefile large3 becomes symlink
   [255]
 #endif
   $ cd bigfile-repo
   $ hg strip --no-backup 2
   0 files updated, 0 files merged, 2 files removed, 0 files unresolved
   $ cd ..
   $ rm -rf largefiles-repo largefiles-repo-symlink
 
   $ hg lfconvert --size 0.2 bigfile-repo largefiles-repo
   initializing destination largefiles-repo
 
 "lfconvert" converts content correctly
   $ cd largefiles-repo
   $ hg up
   getting changed largefiles
   2 largefiles updated, 0 removed
   4 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg locate
   .hglf/large
   .hglf/sub/maybelarge.dat
   normal1
   sub/normal2
   $ cat normal1
   normal
   $ cat sub/normal2
   alsonormal
   $ md5sum.py large sub/maybelarge.dat
   ec87a838931d4d5d2e94a04644788a55  large
   1276481102f218c981e0324180bafd9f  sub/maybelarge.dat
 
 "lfconvert" adds 'largefiles' to .hg/requires.
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   largefiles
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 "lfconvert" includes a newline at the end of the standin files.
   $ cat .hglf/large .hglf/sub/maybelarge.dat
   2e000fa7e85759c7f4c254d4d9c33ef481e459a7
   34e163be8e43c5631d8b92e9c43ab0bf0fa62b9c
   $ cd ..
 
 add some changesets to rename/remove/merge
   $ cd bigfile-repo
   $ hg mv -q sub stuff
   $ hg commit -m"rename sub/ to stuff/"
   $ hg update -q 1
   $ echo blah >> normal3
   $ echo blah >> sub/normal2
   $ echo blah >> sub/maybelarge.dat
   $ md5sum.py sub/maybelarge.dat
   1dd0b99ff80e19cff409702a1d3f5e15  sub/maybelarge.dat
   $ hg commit -A -m"add normal3, modify sub/*"
   adding normal3
   created new head
   $ hg rm large normal3
   $ hg commit -q -m"remove large, normal3"
   $ hg merge
   tool internal:merge (for pattern stuff/maybelarge.dat) can't handle binary
   no tool found to merge stuff/maybelarge.dat
   file 'stuff/maybelarge.dat' needs to be resolved.
   You can keep (l)ocal [working copy], take (o)ther [merge rev], or leave (u)nresolved.
   What do you want to do? u
   merging sub/normal2 and stuff/normal2 to stuff/normal2
   0 files updated, 1 files merged, 0 files removed, 1 files unresolved
   use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
   [1]
   $ hg cat -r . sub/maybelarge.dat > stuff/maybelarge.dat
   $ hg resolve -m stuff/maybelarge.dat
   (no more unresolved files)
   $ hg commit -m"merge"
   $ hg log -G --template "{rev}:{node|short}  {desc|firstline}\n"
   @    5:4884f215abda  merge
   |\
   | o  4:7285f817b77e  remove large, normal3
   | |
   | o  3:67e3892e3534  add normal3, modify sub/*
   | |
   o |  2:c96c8beb5d56  rename sub/ to stuff/
   |/
   o  1:020c65d24e11  add sub/*
   |
   o  0:117b8328f97a  add large, normal1
   
   $ cd ..
 
 lfconvert with rename, merge, and remove
   $ rm -rf largefiles-repo
   $ hg lfconvert --size 0.2 bigfile-repo largefiles-repo
   initializing destination largefiles-repo
   $ cd largefiles-repo
   $ hg log -G --template "{rev}:{node|short}  {desc|firstline}\n"
   o    5:9cc5aa7204f0  merge
   |\
   | o  4:a5a02de7a8e4  remove large, normal3
   | |
   | o  3:55759520c76f  add normal3, modify sub/*
   | |
   o |  2:261ad3f3f037  rename sub/ to stuff/
   |/
   o  1:334e5237836d  add sub/*
   |
   o  0:d4892ec57ce2  add large, normal1
   
   $ hg locate -r 2
   .hglf/large
   .hglf/stuff/maybelarge.dat
   normal1
   stuff/normal2
   $ hg locate -r 3
   .hglf/large
   .hglf/sub/maybelarge.dat
   normal1
   normal3
   sub/normal2
   $ hg locate -r 4
   .hglf/sub/maybelarge.dat
   normal1
   sub/normal2
   $ hg locate -r 5
   .hglf/stuff/maybelarge.dat
   normal1
   stuff/normal2
   $ hg update
   getting changed largefiles
   1 largefiles updated, 0 removed
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cat stuff/normal2
   alsonormal
   blah
   $ md5sum.py stuff/maybelarge.dat
   1dd0b99ff80e19cff409702a1d3f5e15  stuff/maybelarge.dat
   $ cat .hglf/stuff/maybelarge.dat
   76236b6a2c6102826c61af4297dd738fb3b1de38
   $ cd ..
 
 "lfconvert" error cases
   $ hg lfconvert http://localhost/foo foo
   abort: http://localhost/foo is not a local Mercurial repo
   [255]
   $ hg lfconvert foo ssh://localhost/foo
   abort: ssh://localhost/foo is not a local Mercurial repo
   [255]
   $ hg lfconvert nosuchrepo foo
   abort: repository nosuchrepo not found
   [255]
   $ hg share -q -U bigfile-repo shared
   $ printf 'bogus' > shared/.hg/sharedpath
   $ hg lfconvert shared foo
   abort: .hg/sharedpath points to nonexistent directory $TESTTMP/bogus
   [255]
   $ hg lfconvert bigfile-repo largefiles-repo
   initializing destination largefiles-repo
   abort: repository largefiles-repo already exists
   [255]
 
 add another largefile to the new largefiles repo
   $ cd largefiles-repo
   $ dd if=/dev/zero bs=1k count=1k > anotherlarge 2> /dev/null
   $ hg add --lfsize=1 anotherlarge
   $ hg commit -m "add anotherlarge (should be a largefile)"
   $ cat .hglf/anotherlarge
   3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3
   $ hg tag mytag
   $ cd ..
 
 round-trip: converting back to a normal (non-largefiles) repo with
 "lfconvert --to-normal" should give the same as ../bigfile-repo.  The
 convert extension is disabled to show config items can be loaded without it.
   $ cd largefiles-repo
   $ hg --config extensions.convert=! lfconvert --to-normal . ../normal-repo
   initializing destination ../normal-repo
   0 additional largefiles cached
   scanning source...
   sorting...
   converting...
   7 add large, normal1
   6 add sub/*
   5 rename sub/ to stuff/
   4 add normal3, modify sub/*
   3 remove large, normal3
   2 merge
   1 add anotherlarge (should be a largefile)
   0 Added tag mytag for changeset 17126745edfd
   $ cd ../normal-repo
   $ cat >> .hg/hgrc <<EOF
   > [extensions]
   > largefiles = !
   > EOF
 
   $ hg log -G --template "{rev}:{node|short}  {desc|firstline}\n"
   o  7:b5fedc110b9d  Added tag mytag for changeset 867ab992ecf4
   |
   o  6:867ab992ecf4  add anotherlarge (should be a largefile)
   |
   o    5:4884f215abda  merge
   |\
   | o  4:7285f817b77e  remove large, normal3
   | |
   | o  3:67e3892e3534  add normal3, modify sub/*
   | |
   o |  2:c96c8beb5d56  rename sub/ to stuff/
   |/
   o  1:020c65d24e11  add sub/*
   |
   o  0:117b8328f97a  add large, normal1
   
   $ hg update
   5 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg locate
   .hgtags
   anotherlarge
   normal1
   stuff/maybelarge.dat
   stuff/normal2
   $ [ -d .hg/largefiles ] && echo fail || echo pass
   pass
 
   $ cd ..
 
 Clearing the usercache ensures that commitctx doesn't try to cache largefiles
 from the working dir on a convert.
   $ rm "${USERCACHE}"/*
   $ hg convert largefiles-repo
   assuming destination largefiles-repo-hg
   initializing destination largefiles-repo-hg repository
   scanning source...
   sorting...
   converting...
   7 add large, normal1
   6 add sub/*
   5 rename sub/ to stuff/
   4 add normal3, modify sub/*
   3 remove large, normal3
   2 merge
   1 add anotherlarge (should be a largefile)
   0 Added tag mytag for changeset 17126745edfd
 
   $ hg -R largefiles-repo-hg log -G --template "{rev}:{node|short}  {desc|firstline}\n"
   o  7:2f08f66459b7  Added tag mytag for changeset 17126745edfd
   |
   o  6:17126745edfd  add anotherlarge (should be a largefile)
   |
   o    5:9cc5aa7204f0  merge
   |\
   | o  4:a5a02de7a8e4  remove large, normal3
   | |
   | o  3:55759520c76f  add normal3, modify sub/*
   | |
   o |  2:261ad3f3f037  rename sub/ to stuff/
   |/
   o  1:334e5237836d  add sub/*
   |
   o  0:d4892ec57ce2  add large, normal1
   
 Verify will fail (for now) if the usercache is purged before converting, since
 largefiles are not cached in the converted repo's local store by the conversion
 process.
   $ cd largefiles-repo-hg
   $ cat >> .hg/hgrc <<EOF
   > [experimental]
   > evolution.createmarkers=True
   > EOF
   $ hg debugobsolete `hg log -r tip -T "{node}"`
   1 new obsolescence markers
   obsoleted 1 changesets
   $ cd ..
 
   $ hg -R largefiles-repo-hg verify --large --lfa
   checking changesets
   checking manifests
   crosschecking files in changesets and manifests
   checking files
   checked 8 changesets with 13 changes to 9 files
   searching 7 changesets for largefiles
   changeset 0:d4892ec57ce2: large references missing $TESTTMP/largefiles-repo-hg/.hg/largefiles/2e000fa7e85759c7f4c254d4d9c33ef481e459a7
   changeset 1:334e5237836d: sub/maybelarge.dat references missing $TESTTMP/largefiles-repo-hg/.hg/largefiles/34e163be8e43c5631d8b92e9c43ab0bf0fa62b9c
   changeset 2:261ad3f3f037: stuff/maybelarge.dat references missing $TESTTMP/largefiles-repo-hg/.hg/largefiles/34e163be8e43c5631d8b92e9c43ab0bf0fa62b9c
   changeset 3:55759520c76f: sub/maybelarge.dat references missing $TESTTMP/largefiles-repo-hg/.hg/largefiles/76236b6a2c6102826c61af4297dd738fb3b1de38
   changeset 5:9cc5aa7204f0: stuff/maybelarge.dat references missing $TESTTMP/largefiles-repo-hg/.hg/largefiles/76236b6a2c6102826c61af4297dd738fb3b1de38
   changeset 6:17126745edfd: anotherlarge references missing $TESTTMP/largefiles-repo-hg/.hg/largefiles/3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3
   verified existence of 6 revisions of 4 largefiles
   [1]
   $ hg -R largefiles-repo-hg showconfig paths
   [1]
 
 
 Avoid a traceback if a largefile isn't available (issue3519)
 
 Ensure the largefile can be cached in the source if necessary
   $ hg clone -U largefiles-repo issue3519
   $ rm -f "${USERCACHE}"/*
   $ hg -R issue3519 branch -q mybranch
   $ hg -R issue3519 ci -m 'change branch name only'
   $ hg lfconvert --to-normal issue3519 normalized3519
   initializing destination normalized3519
   4 additional largefiles cached
   scanning source...
   sorting...
   converting...
   8 add large, normal1
   7 add sub/*
   6 rename sub/ to stuff/
   5 add normal3, modify sub/*
   4 remove large, normal3
   3 merge
   2 add anotherlarge (should be a largefile)
   1 Added tag mytag for changeset 17126745edfd
   0 change branch name only
 
 Ensure empty commits aren't lost in the conversion
   $ hg -R normalized3519 log -r tip -T '{desc}\n'
   change branch name only
 
 Ensure the abort message is useful if a largefile is entirely unavailable
   $ rm -rf normalized3519
   $ rm "${USERCACHE}"/*
   $ rm issue3519/.hg/largefiles/*
   $ rm largefiles-repo/.hg/largefiles/*
   $ hg lfconvert --to-normal issue3519 normalized3519
   initializing destination normalized3519
   large: largefile 2e000fa7e85759c7f4c254d4d9c33ef481e459a7 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   large: largefile 2e000fa7e85759c7f4c254d4d9c33ef481e459a7 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   sub/maybelarge.dat: largefile 34e163be8e43c5631d8b92e9c43ab0bf0fa62b9c not available from file:/*/$TESTTMP/largefiles-repo (glob)
   large: largefile 2e000fa7e85759c7f4c254d4d9c33ef481e459a7 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   stuff/maybelarge.dat: largefile 34e163be8e43c5631d8b92e9c43ab0bf0fa62b9c not available from file:/*/$TESTTMP/largefiles-repo (glob)
   large: largefile 2e000fa7e85759c7f4c254d4d9c33ef481e459a7 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   sub/maybelarge.dat: largefile 76236b6a2c6102826c61af4297dd738fb3b1de38 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   sub/maybelarge.dat: largefile 76236b6a2c6102826c61af4297dd738fb3b1de38 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   stuff/maybelarge.dat: largefile 76236b6a2c6102826c61af4297dd738fb3b1de38 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   anotherlarge: largefile 3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   stuff/maybelarge.dat: largefile 76236b6a2c6102826c61af4297dd738fb3b1de38 not available from file:/*/$TESTTMP/largefiles-repo (glob)
   0 additional largefiles cached
   11 largefiles failed to download
   abort: all largefiles must be present locally
   [255]
 
 

tests/test-lfs-largefiles.t

@@ -1,360 +1,360 b''
 #require no-reposimplestore no-chg
 
 This tests the interaction between the largefiles and lfs extensions, and
 conversion from largefiles -> lfs.
 
   $ cat >> $HGRCPATH << EOF
   > [extensions]
   > largefiles =
   > 
   > [lfs]
   > # standin files are 41 bytes.  Stay bigger for clarity.
   > threshold = 42
   > EOF
 
 Setup a repo with a normal file and a largefile, above and below the lfs
 threshold to test lfconvert.  *.txt start life as a normal file; *.bin start as
 an lfs/largefile.
 
   $ hg init largefiles
   $ cd largefiles
   $ echo 'normal' > normal.txt
   $ echo 'normal above lfs threshold 0000000000000000000000000' > lfs.txt
   $ hg ci -Am 'normal.txt'
   adding lfs.txt
   adding normal.txt
   $ echo 'largefile' > large.bin
   $ echo 'largefile above lfs threshold 0000000000000000000000' > lfs.bin
   $ hg add --large large.bin lfs.bin
   $ hg ci -m 'add largefiles'
 
   $ cat >> $HGRCPATH << EOF
   > [extensions]
   > lfs =
   > EOF
 
 Add an lfs file and normal file that collide with files on the other branch.
 large.bin is added as a normal file, and is named as such only to clash with the
 largefile on the other branch.
 
   $ hg up -q '.^'
   $ echo 'below lfs threshold' > large.bin
   $ echo 'lfs above the lfs threshold for length 0000000000000' > lfs.bin
   $ hg ci -Am 'add with lfs extension'
   adding large.bin
   adding lfs.bin
   created new head
 
   $ hg log -G
   @  changeset:   2:e989d0fa3764
   |  tag:         tip
   |  parent:      0:29361292f54d
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     add with lfs extension
   |
   | o  changeset:   1:6513aaab9ca0
   |/   user:        test
   |    date:        Thu Jan 01 00:00:00 1970 +0000
   |    summary:     add largefiles
   |
   o  changeset:   0:29361292f54d
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     normal.txt
   
 --------------------------------------------------------------------------------
 Merge largefiles into lfs branch
 
 The largefiles extension will prompt to use the normal or largefile when merged
 into the lfs files.  `hg manifest` will show standins if present.  They aren't,
 because largefiles merge doesn't merge content.  If it did, selecting (n)ormal
 would convert to lfs on commit, if appropriate.
 
 BUG: Largefiles isn't running the merge tool, like when two lfs files are
 merged.  This is probably by design, but it should probably at least prompt if
 content should be taken from (l)ocal or (o)ther as well.
 
   $ hg --config ui.interactive=True merge 6513aaab9ca0 <<EOF
   > n
   > n
   > EOF
   remote turned local normal file large.bin into a largefile
   use (l)argefile or keep (n)ormal file? n
   remote turned local normal file lfs.bin into a largefile
   use (l)argefile or keep (n)ormal file? n
   0 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m 'merge lfs with largefiles -> normal'
   $ hg manifest
   large.bin
   lfs.bin
   lfs.txt
   normal.txt
 
 The merged lfs.bin resolved to lfs because the (n)ormal option was picked.  The
 lfs.txt file is unchanged by the merge, because it was added before lfs was
 enabled, and the content didn't change.
   $ hg debugdata lfs.bin 0
   version https://git-lfs.github.com/spec/v1
   oid sha256:81c7492b2c05e130431f65a87651b54a30c5da72c99ce35a1e9b9872a807312b
   size 53
   x-is-binary 0
   $ hg debugdata lfs.txt 0
   normal above lfs threshold 0000000000000000000000000
 
 Another filelog entry is NOT made by the merge, so nothing is committed as lfs.
   $ hg log -r . -T '{join(lfs_files, ", ")}\n'
   
 
 Replay the last merge, but pick (l)arge this time.  The manifest will show any
 standins.
 
   $ hg up -Cq e989d0fa3764
 
   $ hg --config ui.interactive=True merge 6513aaab9ca0 <<EOF
   > l
   > l
   > EOF
   remote turned local normal file large.bin into a largefile
   use (l)argefile or keep (n)ormal file? l
   remote turned local normal file lfs.bin into a largefile
   use (l)argefile or keep (n)ormal file? l
   getting changed largefiles
   2 largefiles updated, 0 removed
   2 files updated, 0 files merged, 2 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m 'merge lfs with largefiles -> large'
   created new head
   $ hg manifest
   .hglf/large.bin
   .hglf/lfs.bin
   lfs.txt
   normal.txt
 
 --------------------------------------------------------------------------------
 Merge lfs into largefiles branch
 
   $ hg up -Cq 6513aaab9ca0
   $ hg --config ui.interactive=True merge e989d0fa3764 <<EOF
   > n
   > n
   > EOF
   remote turned local largefile large.bin into a normal file
   keep (l)argefile or use (n)ormal file? n
   remote turned local largefile lfs.bin into a normal file
   keep (l)argefile or use (n)ormal file? n
   getting changed largefiles
   0 largefiles updated, 0 removed
   2 files updated, 0 files merged, 2 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m 'merge largefiles with lfs -> normal'
   created new head
   $ hg manifest
   large.bin
   lfs.bin
   lfs.txt
   normal.txt
 
 The merged lfs.bin got converted to lfs because the (n)ormal option was picked.
 The lfs.txt file is unchanged by the merge, because it was added before lfs was
 enabled.
   $ hg debugdata lfs.bin 0
   version https://git-lfs.github.com/spec/v1
   oid sha256:81c7492b2c05e130431f65a87651b54a30c5da72c99ce35a1e9b9872a807312b
   size 53
   x-is-binary 0
   $ hg debugdata lfs.txt 0
   normal above lfs threshold 0000000000000000000000000
 
 Another filelog entry is NOT made by the merge, so nothing is committed as lfs.
   $ hg log -r . -T '{join(lfs_files, ", ")}\n'
   
 
 Replay the last merge, but pick (l)arge this time.  The manifest will show the
 standins.
 
   $ hg up -Cq 6513aaab9ca0
 
   $ hg --config ui.interactive=True merge e989d0fa3764 <<EOF
   > l
   > l
   > EOF
   remote turned local largefile large.bin into a normal file
   keep (l)argefile or use (n)ormal file? l
   remote turned local largefile lfs.bin into a normal file
   keep (l)argefile or use (n)ormal file? l
   0 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m 'merge largefiles with lfs -> large'
   created new head
   $ hg manifest
   .hglf/large.bin
   .hglf/lfs.bin
   lfs.txt
   normal.txt
 
 --------------------------------------------------------------------------------
 
 When both largefiles and lfs are configured to add by size, the tie goes to
 largefiles since it hooks cmdutil.add() and lfs hooks the filelog write in the
 commit.  By the time the commit occurs, the tracked file is smaller than the
 threshold (assuming it is > 41, so the standins don't become lfs objects).
 
   $ "$PYTHON" -c 'import sys ; sys.stdout.write("y\n" * 1048576)' > large_by_size.bin
   $ hg --config largefiles.minsize=1 ci -Am 'large by size'
   adding large_by_size.bin as a largefile
   $ hg manifest
   .hglf/large.bin
   .hglf/large_by_size.bin
   .hglf/lfs.bin
   lfs.txt
   normal.txt
 
   $ hg rm large_by_size.bin
   $ hg ci -m 'remove large_by_size.bin'
 
 Largefiles doesn't do anything special with diff, so it falls back to diffing
 the standins.  Extdiff also is standin based comparison.  Diff and extdiff both
 work on the original file for lfs objects.
 
 Largefile -> lfs transition
   $ hg diff -r 1 -r 3
   diff -r 6513aaab9ca0 -r dcc5ce63e252 .hglf/large.bin
   --- a/.hglf/large.bin	Thu Jan 01 00:00:00 1970 +0000
   +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
   @@ -1,1 +0,0 @@
   -cef9a458373df9b0743a0d3c14d0c66fb19b8629
   diff -r 6513aaab9ca0 -r dcc5ce63e252 .hglf/lfs.bin
   --- a/.hglf/lfs.bin	Thu Jan 01 00:00:00 1970 +0000
   +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
   @@ -1,1 +0,0 @@
   -557fb6309cef935e1ac2c8296508379e4b15a6e6
   diff -r 6513aaab9ca0 -r dcc5ce63e252 large.bin
   --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
   +++ b/large.bin	Thu Jan 01 00:00:00 1970 +0000
   @@ -0,0 +1,1 @@
   +below lfs threshold
   diff -r 6513aaab9ca0 -r dcc5ce63e252 lfs.bin
   --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
   +++ b/lfs.bin	Thu Jan 01 00:00:00 1970 +0000
   @@ -0,0 +1,1 @@
   +lfs above the lfs threshold for length 0000000000000
 
 lfs -> largefiles transition
   $ hg diff -r 2 -r 6
   diff -r e989d0fa3764 -r 95e1e80325c8 .hglf/large.bin
   --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
   +++ b/.hglf/large.bin	Thu Jan 01 00:00:00 1970 +0000
   @@ -0,0 +1,1 @@
   +cef9a458373df9b0743a0d3c14d0c66fb19b8629
   diff -r e989d0fa3764 -r 95e1e80325c8 .hglf/lfs.bin
   --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
   +++ b/.hglf/lfs.bin	Thu Jan 01 00:00:00 1970 +0000
   @@ -0,0 +1,1 @@
   +557fb6309cef935e1ac2c8296508379e4b15a6e6
   diff -r e989d0fa3764 -r 95e1e80325c8 large.bin
   --- a/large.bin	Thu Jan 01 00:00:00 1970 +0000
   +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
   @@ -1,1 +0,0 @@
   -below lfs threshold
   diff -r e989d0fa3764 -r 95e1e80325c8 lfs.bin
   --- a/lfs.bin	Thu Jan 01 00:00:00 1970 +0000
   +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
   @@ -1,1 +0,0 @@
   -lfs above the lfs threshold for length 0000000000000
 
 A largefiles repo can be converted to lfs.  The lfconvert command uses the
 convert extension under the hood with --to-normal.  So the --config based
 parameters are available, but not --authormap, --branchmap, etc.
 
   $ cd ..
   $ hg lfconvert --to-normal largefiles nolargefiles 2>&1
   initializing destination nolargefiles
   0 additional largefiles cached
   scanning source...
   sorting...
   converting...
   8 normal.txt
   7 add largefiles
   6 add with lfs extension
   5 merge lfs with largefiles -> normal
   4 merge lfs with largefiles -> large
   3 merge largefiles with lfs -> normal
   2 merge largefiles with lfs -> large
   1 large by size
   0 remove large_by_size.bin
   $ cd nolargefiles
 
 The requirement is added to the destination repo.
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   lfs
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
   $ hg log -r 'all()' -G -T '{rev} {join(lfs_files, ", ")} ({desc})\n'
   o  8 large_by_size.bin (remove large_by_size.bin)
   |
   o  7 large_by_size.bin (large by size)
   |
   o    6  (merge largefiles with lfs -> large)
   |\
   +---o  5  (merge largefiles with lfs -> normal)
   | |/
   +---o  4 lfs.bin (merge lfs with largefiles -> large)
   | |/
   +---o  3  (merge lfs with largefiles -> normal)
   | |/
   | o  2 lfs.bin (add with lfs extension)
   | |
   o |  1 lfs.bin (add largefiles)
   |/
   o  0 lfs.txt (normal.txt)
   
   $ hg debugdata lfs.bin 0
   version https://git-lfs.github.com/spec/v1
   oid sha256:2172a5bd492dd41ec533b9bb695f7691b6351719407ac797f0ccad5348c81e62
   size 53
   x-is-binary 0
   $ hg debugdata lfs.bin 1
   version https://git-lfs.github.com/spec/v1
   oid sha256:81c7492b2c05e130431f65a87651b54a30c5da72c99ce35a1e9b9872a807312b
   size 53
   x-is-binary 0
   $ hg debugdata lfs.bin 2
   version https://git-lfs.github.com/spec/v1
   oid sha256:2172a5bd492dd41ec533b9bb695f7691b6351719407ac797f0ccad5348c81e62
   size 53
   x-is-binary 0
   $ hg debugdata lfs.bin 3
   abort: invalid revision identifier 3
   [255]
 
 No diffs when comparing merge and p1 that kept p1's changes.  Diff of lfs to
 largefiles no longer operates in standin files.
 
 This `head -n 20` looks dumb (since we expect no output), but if something
 breaks you can get 1048576 lines of +y in the output, which takes a looooooong
 time to print.
   $ hg diff -r 2:3 | head -n 20
   $ hg diff -r 2:6
   diff -r e989d0fa3764 -r 752e3a0d8488 large.bin
   --- a/large.bin	Thu Jan 01 00:00:00 1970 +0000
   +++ b/large.bin	Thu Jan 01 00:00:00 1970 +0000
   @@ -1,1 +1,1 @@
   -below lfs threshold
   +largefile
   diff -r e989d0fa3764 -r 752e3a0d8488 lfs.bin
   --- a/lfs.bin	Thu Jan 01 00:00:00 1970 +0000
   +++ b/lfs.bin	Thu Jan 01 00:00:00 1970 +0000
   @@ -1,1 +1,1 @@
   -lfs above the lfs threshold for length 0000000000000
   +largefile above lfs threshold 0000000000000000000000

tests/test-narrow-clone-no-ellipsis.t

@@ -1,165 +1,165 b''
   $ . "$TESTDIR/narrow-library.sh"
 
   $ hg init master
   $ cd master
   $ mkdir dir
   $ mkdir dir/src
   $ cd dir/src
   $ for x in `$TESTDIR/seq.py 20`; do echo $x > "f$x"; hg add "f$x"; hg commit -m "Commit src $x"; done
   $ cd ..
   $ mkdir tests
   $ cd tests
   $ for x in `$TESTDIR/seq.py 20`; do echo $x > "t$x"; hg add "t$x"; hg commit -m "Commit test $x"; done
   $ cd ../../..
 
 narrow clone a file, f10
 
   $ hg clone --narrow ssh://user@dummy/master narrow --noupdate --include "dir/src/f10"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 40 changesets with 1 changes to 1 files
   new changesets *:* (glob)
   $ cd narrow
   $ cat .hg/requires | grep -v generaldelta
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   narrowhg-experimental
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ hg tracked
   I path:dir/src/f10
   $ hg update
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ find * | sort
   dir
   dir/src
   dir/src/f10
   $ cat dir/src/f10
   10
 
   $ cd ..
 
 narrow clone a directory, tests/, except tests/t19
 
   $ hg clone --narrow ssh://user@dummy/master narrowdir --noupdate --include "dir/tests/" --exclude "dir/tests/t19"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 40 changesets with 19 changes to 19 files
   new changesets *:* (glob)
   $ cd narrowdir
   $ hg tracked
   I path:dir/tests
   X path:dir/tests/t19
   $ hg update
   19 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ find * | sort
   dir
   dir/tests
   dir/tests/t1
   dir/tests/t10
   dir/tests/t11
   dir/tests/t12
   dir/tests/t13
   dir/tests/t14
   dir/tests/t15
   dir/tests/t16
   dir/tests/t17
   dir/tests/t18
   dir/tests/t2
   dir/tests/t20
   dir/tests/t3
   dir/tests/t4
   dir/tests/t5
   dir/tests/t6
   dir/tests/t7
   dir/tests/t8
   dir/tests/t9
 
   $ cd ..
 
 narrow clone everything but a directory (tests/)
 
   $ hg clone --narrow ssh://user@dummy/master narrowroot --noupdate --exclude "dir/tests"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 40 changesets with 20 changes to 20 files
   new changesets *:* (glob)
   $ cd narrowroot
   $ hg tracked
   I path:.
   X path:dir/tests
   $ hg update
   20 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ find * | sort
   dir
   dir/src
   dir/src/f1
   dir/src/f10
   dir/src/f11
   dir/src/f12
   dir/src/f13
   dir/src/f14
   dir/src/f15
   dir/src/f16
   dir/src/f17
   dir/src/f18
   dir/src/f19
   dir/src/f2
   dir/src/f20
   dir/src/f3
   dir/src/f4
   dir/src/f5
   dir/src/f6
   dir/src/f7
   dir/src/f8
   dir/src/f9
 
   $ cd ..
 
 Testing the --narrowspec flag to clone
 
   $ cat >> narrowspecs <<EOF
   > %include foo
   > [include]
   > path:dir/tests/
   > path:dir/src/f12
   > EOF
 
   $ hg clone ssh://user@dummy/master specfile --narrowspec narrowspecs
   reading narrowspec from '$TESTTMP/narrowspecs'
   config error: cannot specify other files using '%include' in narrowspec
   [30]
 
   $ cat > narrowspecs <<EOF
   > [include]
   > path:dir/tests/
   > path:dir/src/f12
   > EOF
 
   $ hg clone ssh://user@dummy/master specfile --narrowspec narrowspecs
   reading narrowspec from '$TESTTMP/narrowspecs'
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 40 changesets with 21 changes to 21 files
   new changesets 681085829a73:26ce255d5b5d
   updating to branch default
   21 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd specfile
   $ hg tracked
   I path:dir/src/f12
   I path:dir/tests
   $ cd ..

tests/test-narrow-clone-stream.t

@@ -1,102 +1,102 b''
 #testcases tree flat-fncache flat-nofncache
 
 Tests narrow stream clones
 
   $ . "$TESTDIR/narrow-library.sh"
 
 #if tree
   $ cat << EOF >> $HGRCPATH
   > [experimental]
   > treemanifest = 1
   > EOF
 #endif
 
 #if flat-nofncache
   $ cat << EOF >> $HGRCPATH
   > [format]
   > usefncache = 0
   > EOF
 #endif
 
 Server setup
 
   $ hg init master
   $ cd master
   $ mkdir dir
   $ mkdir dir/src
   $ cd dir/src
   $ for x in `$TESTDIR/seq.py 20`; do echo $x > "F$x"; hg add "F$x"; hg commit -m "Commit src $x"; done
 
   $ cd ..
   $ mkdir tests
   $ cd tests
   $ for x in `$TESTDIR/seq.py 20`; do echo $x > "F$x"; hg add "F$x"; hg commit -m "Commit src $x"; done
   $ cd ../../..
 
 Trying to stream clone when the server does not support it
 
   $ hg clone --narrow ssh://user@dummy/master narrow --noupdate --include "dir/src/F10" --stream
   streaming all changes
   remote: abort: server does not support narrow stream clones
   abort: pull failed on remote
   [100]
 
 Enable stream clone on the server
 
   $ echo "[experimental]" >> master/.hg/hgrc
   $ echo "server.stream-narrow-clones=True" >> master/.hg/hgrc
 
 Cloning a specific file when stream clone is supported
 
   $ hg clone --narrow ssh://user@dummy/master narrow --noupdate --include "dir/src/F10" --stream
   streaming all changes
   * files to transfer, * KB of data (glob)
   transferred * KB in * seconds (* */sec) (glob)
 
   $ cd narrow
   $ ls -A
   .hg
   $ hg tracked
   I path:dir/src/F10
 
 Making sure we have the correct set of requirements
 
   $ cat .hg/requires
   dotencode (tree !)
   dotencode (flat-fncache !)
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache (tree !)
   fncache (flat-fncache !)
   generaldelta
   narrowhg-experimental
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   treemanifest (tree !)
 
 Making sure store has the required files
 
   $ ls .hg/store/
   00changelog.i
   00manifest.i
   data
   fncache (tree !)
   fncache (flat-fncache !)
   meta (tree !)
   narrowspec
   undo
   undo.backupfiles
   undo.narrowspec
   undo.phaseroots
 
 Checking that repository has all the required data and not broken
 
   $ hg verify
   checking changesets
   checking manifests
   checking directory manifests (tree !)
   crosschecking files in changesets and manifests
   checking files
   checked 40 changesets with 1 changes to 1 files

tests/test-narrow-clone.t

@@ -1,298 +1,298 b''
   $ . "$TESTDIR/narrow-library.sh"
 
   $ hg init master
   $ cd master
   $ cat >> .hg/hgrc <<EOF
   > [narrow]
   > serveellipses=True
   > EOF
   $ mkdir dir
   $ mkdir dir/src
   $ cd dir/src
   $ for x in `$TESTDIR/seq.py 20`; do echo $x > "f$x"; hg add "f$x"; hg commit -m "Commit src $x"; done
   $ cd ..
   $ mkdir tests
   $ cd tests
   $ for x in `$TESTDIR/seq.py 20`; do echo $x > "t$x"; hg add "t$x"; hg commit -m "Commit test $x"; done
   $ cd ../../..
 
 Only path: and rootfilesin: pattern prefixes are allowed
 
   $ hg clone --narrow ssh://user@dummy/master badnarrow --noupdate --include 'glob:**'
   abort: invalid prefix on narrow pattern: glob:**
   (narrow patterns must begin with one of the following: path:, rootfilesin:)
   [255]
 
   $ hg clone --narrow ssh://user@dummy/master badnarrow --noupdate --exclude 'set:ignored'
   abort: invalid prefix on narrow pattern: set:ignored
   (narrow patterns must begin with one of the following: path:, rootfilesin:)
   [255]
 
 narrow clone a file, f10
 
   $ hg clone --narrow ssh://user@dummy/master narrow --noupdate --include "dir/src/f10"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 3 changesets with 1 changes to 1 files
   new changesets *:* (glob)
   $ cd narrow
   $ cat .hg/requires | grep -v generaldelta
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   narrowhg-experimental
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ hg tracked
   I path:dir/src/f10
   $ hg tracked
   I path:dir/src/f10
   $ hg update
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ find * | sort
   dir
   dir/src
   dir/src/f10
   $ cat dir/src/f10
   10
 
   $ cd ..
 
 local-to-local narrow clones work
 
   $ hg clone --narrow master narrow-via-localpeer --noupdate --include "dir/src/f10"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 3 changesets with 1 changes to 1 files
   new changesets 5d21aaea77f8:26ce255d5b5d
   $ hg tracked -R narrow-via-localpeer
   I path:dir/src/f10
   $ rm -Rf narrow-via-localpeer
 
 narrow clone with a newline should fail
 
   $ hg clone --narrow ssh://user@dummy/master narrow_fail --noupdate --include 'dir/src/f10
   > '
   abort: newlines are not allowed in narrowspec paths
   [255]
 
 narrow clone a directory, tests/, except tests/t19
 
   $ hg clone --narrow ssh://user@dummy/master narrowdir --noupdate --include "dir/tests/" --exclude "dir/tests/t19"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 21 changesets with 19 changes to 19 files
   new changesets *:* (glob)
   $ cd narrowdir
   $ hg tracked
   I path:dir/tests
   X path:dir/tests/t19
   $ hg tracked
   I path:dir/tests
   X path:dir/tests/t19
   $ hg update
   19 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ find * | sort
   dir
   dir/tests
   dir/tests/t1
   dir/tests/t10
   dir/tests/t11
   dir/tests/t12
   dir/tests/t13
   dir/tests/t14
   dir/tests/t15
   dir/tests/t16
   dir/tests/t17
   dir/tests/t18
   dir/tests/t2
   dir/tests/t20
   dir/tests/t3
   dir/tests/t4
   dir/tests/t5
   dir/tests/t6
   dir/tests/t7
   dir/tests/t8
   dir/tests/t9
 
   $ cd ..
 
 narrow clone everything but a directory (tests/)
 
   $ hg clone --narrow ssh://user@dummy/master narrowroot --noupdate --exclude "dir/tests"
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 21 changesets with 20 changes to 20 files
   new changesets *:* (glob)
   $ cd narrowroot
   $ hg tracked
   I path:.
   X path:dir/tests
   $ hg tracked
   I path:.
   X path:dir/tests
   $ hg update
   20 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ find * | sort
   dir
   dir/src
   dir/src/f1
   dir/src/f10
   dir/src/f11
   dir/src/f12
   dir/src/f13
   dir/src/f14
   dir/src/f15
   dir/src/f16
   dir/src/f17
   dir/src/f18
   dir/src/f19
   dir/src/f2
   dir/src/f20
   dir/src/f3
   dir/src/f4
   dir/src/f5
   dir/src/f6
   dir/src/f7
   dir/src/f8
   dir/src/f9
 
   $ cd ..
 
 narrow clone no paths at all
 
   $ hg clone --narrow ssh://user@dummy/master narrowempty --noupdate
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 1 changesets with 0 changes to 0 files
   new changesets * (glob)
   $ cd narrowempty
   $ hg tracked
   $ hg update
   0 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ ls -A
   .hg
 
   $ cd ..
 
 simple clone
   $ hg clone ssh://user@dummy/master simpleclone
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 40 changesets with 40 changes to 40 files
   new changesets * (glob)
   updating to branch default
   40 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd simpleclone
   $ find * | sort
   dir
   dir/src
   dir/src/f1
   dir/src/f10
   dir/src/f11
   dir/src/f12
   dir/src/f13
   dir/src/f14
   dir/src/f15
   dir/src/f16
   dir/src/f17
   dir/src/f18
   dir/src/f19
   dir/src/f2
   dir/src/f20
   dir/src/f3
   dir/src/f4
   dir/src/f5
   dir/src/f6
   dir/src/f7
   dir/src/f8
   dir/src/f9
   dir/tests
   dir/tests/t1
   dir/tests/t10
   dir/tests/t11
   dir/tests/t12
   dir/tests/t13
   dir/tests/t14
   dir/tests/t15
   dir/tests/t16
   dir/tests/t17
   dir/tests/t18
   dir/tests/t19
   dir/tests/t2
   dir/tests/t20
   dir/tests/t3
   dir/tests/t4
   dir/tests/t5
   dir/tests/t6
   dir/tests/t7
   dir/tests/t8
   dir/tests/t9
 
   $ cd ..
 
 Testing the --narrowspec flag to clone
 
   $ cat >> narrowspecs <<EOF
   > %include foo
   > [include]
   > path:dir/tests/
   > path:dir/src/f12
   > EOF
 
   $ hg clone ssh://user@dummy/master specfile --narrowspec narrowspecs
   reading narrowspec from '$TESTTMP/narrowspecs'
   config error: cannot specify other files using '%include' in narrowspec
   [30]
 
   $ cat > narrowspecs <<EOF
   > [include]
   > path:dir/tests/
   > path:dir/src/f12
   > EOF
 
   $ hg clone ssh://user@dummy/master specfile --narrowspec narrowspecs
   reading narrowspec from '$TESTTMP/narrowspecs'
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 23 changesets with 21 changes to 21 files
   new changesets c13e3773edb4:26ce255d5b5d
   updating to branch default
   21 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd specfile
   $ hg tracked
   I path:dir/src/f12
   I path:dir/tests
   $ cd ..
 
 Narrow spec with invalid patterns is rejected
 
   $ cat > narrowspecs <<EOF
   > [include]
   > glob:**
   > EOF
 
   $ hg clone ssh://user@dummy/master badspecfile --narrowspec narrowspecs
   reading narrowspec from '$TESTTMP/narrowspecs'
   abort: invalid prefix on narrow pattern: glob:**
   (narrow patterns must begin with one of the following: path:, rootfilesin:)
   [255]

tests/test-narrow-sparse.t

@@ -1,97 +1,97 b''
 Testing interaction of sparse and narrow when both are enabled on the client
 side and we do a non-ellipsis clone
 
 #testcases tree flat
   $ . "$TESTDIR/narrow-library.sh"
   $ cat << EOF >> $HGRCPATH
   > [extensions]
   > sparse =
   > EOF
 
 #if tree
   $ cat << EOF >> $HGRCPATH
   > [experimental]
   > treemanifest = 1
   > EOF
 #endif
 
   $ hg init master
   $ cd master
 
   $ mkdir inside
   $ echo 'inside' > inside/f
   $ hg add inside/f
   $ hg commit -m 'add inside'
 
   $ mkdir widest
   $ echo 'widest' > widest/f
   $ hg add widest/f
   $ hg commit -m 'add widest'
 
   $ mkdir outside
   $ echo 'outside' > outside/f
   $ hg add outside/f
   $ hg commit -m 'add outside'
 
   $ cd ..
 
 narrow clone the inside file
 
   $ hg clone --narrow ssh://user@dummy/master narrow --include inside/f
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 3 changesets with 1 changes to 1 files
   new changesets *:* (glob)
   updating to branch default
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd narrow
   $ hg tracked
   I path:inside/f
   $ hg files
   inside/f
 
 XXX: we should have a flag in `hg debugsparse` to list the sparse profile
   $ test -f .hg/sparse
   [1]
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   narrowhg-experimental
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   treemanifest (tree !)
 
   $ hg debugrebuilddirstate
 
 We only make the following assertions for the flat test case since in the
 treemanifest test case debugsparse fails with "path ends in directory
 separator: outside/" which seems like a bug unrelated to the regression this is
 testing for.
 
 #if flat
 widening with both sparse and narrow is possible
 
   $ cat >> .hg/hgrc <<EOF
   > [extensions]
   > sparse = 
   > narrow = 
   > EOF
 
   $ hg debugsparse -X outside/f -X widest/f
   $ hg tracked -q --addinclude outside/f
   $ find . -name .hg -prune -o -type f -print | sort
   ./inside/f
 
   $ hg debugsparse -d outside/f
   $ find . -name .hg -prune -o -type f -print | sort
   ./inside/f
   ./outside/f
 #endif

tests/test-phases.t

@@ -1,1060 +1,1060 b''
   $ cat > $TESTTMP/hook.sh << 'EOF'
   > echo "test-hook-close-phase: $HG_NODE:  $HG_OLDPHASE -> $HG_PHASE"
   > EOF
 
   $ cat >> $HGRCPATH << EOF
   > [extensions]
   > phasereport=$TESTDIR/testlib/ext-phase-report.py
   > [hooks]
   > txnclose-phase.test = sh $TESTTMP/hook.sh
   > EOF
 
   $ hglog() { hg log --template "{rev} {phaseidx} {desc}\n" $*; }
   $ mkcommit() {
   >    echo "$1" > "$1"
   >    hg add "$1"
   >    message="$1"
   >    shift
   >    hg ci -m "$message" $*
   > }
 
   $ hg init initialrepo
   $ cd initialrepo
 
 Cannot change null revision phase
 
   $ hg phase --force --secret null
   abort: cannot change null revision phase
   [255]
   $ hg phase null
   -1: public
 
   $ mkcommit A
   test-debug-phase: new rev 0:  x -> 1
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:   -> draft
 
 New commit are draft by default
 
   $ hglog
   0 1 A
 
 Following commit are draft too
 
   $ mkcommit B
   test-debug-phase: new rev 1:  x -> 1
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:   -> draft
 
   $ hglog
   1 1 B
   0 1 A
 
 Working directory phase is secret when its parent is secret.
 
   $ hg phase --force --secret .
   test-debug-phase: move rev 0: 1 -> 2
   test-debug-phase: move rev 1: 1 -> 2
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:  draft -> secret
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:  draft -> secret
   $ hg log -r 'wdir()' -T '{phase}\n'
   secret
   $ hg log -r 'wdir() and public()' -T '{phase}\n'
   $ hg log -r 'wdir() and draft()' -T '{phase}\n'
   $ hg log -r 'wdir() and secret()' -T '{phase}\n'
   secret
 
 Working directory phase is draft when its parent is draft.
 
   $ hg phase --draft .
   test-debug-phase: move rev 1: 2 -> 1
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:  secret -> draft
   $ hg log -r 'wdir()' -T '{phase}\n'
   draft
   $ hg log -r 'wdir() and public()' -T '{phase}\n'
   $ hg log -r 'wdir() and draft()' -T '{phase}\n'
   draft
   $ hg log -r 'wdir() and secret()' -T '{phase}\n'
 
 Working directory phase is secret when a new commit will be created as secret,
 even if the parent is draft.
 
   $ hg log -r 'wdir() and secret()' -T '{phase}\n' \
   > --config phases.new-commit='secret'
   secret
 
 Working directory phase is draft when its parent is public.
 
   $ hg phase --public .
   test-debug-phase: move rev 0: 1 -> 0
   test-debug-phase: move rev 1: 1 -> 0
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:  draft -> public
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:  draft -> public
   $ hg log -r 'wdir()' -T '{phase}\n'
   draft
   $ hg log -r 'wdir() and public()' -T '{phase}\n'
   $ hg log -r 'wdir() and draft()' -T '{phase}\n'
   draft
   $ hg log -r 'wdir() and secret()' -T '{phase}\n'
   $ hg log -r 'wdir() and secret()' -T '{phase}\n' \
   > --config phases.new-commit='secret'
   secret
 
 Draft commit are properly created over public one:
 
   $ hg phase
   1: public
   $ hglog
   1 0 B
   0 0 A
 
   $ mkcommit C
   test-debug-phase: new rev 2:  x -> 1
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:   -> draft
   $ mkcommit D
   test-debug-phase: new rev 3:  x -> 1
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:   -> draft
 
   $ hglog
   3 1 D
   2 1 C
   1 0 B
   0 0 A
 
 Test creating changeset as secret
 
   $ mkcommit E --config phases.new-commit='secret'
   test-debug-phase: new rev 4:  x -> 2
   test-hook-close-phase: a603bfb5a83e312131cebcd05353c217d4d21dde:   -> secret
   $ hglog
   4 2 E
   3 1 D
   2 1 C
   1 0 B
   0 0 A
 
 Test the secret property is inherited
 
   $ mkcommit H
   test-debug-phase: new rev 5:  x -> 2
   test-hook-close-phase: a030c6be5127abc010fcbff1851536552e6951a8:   -> secret
   $ hglog
   5 2 H
   4 2 E
   3 1 D
   2 1 C
   1 0 B
   0 0 A
 
 Even on merge
 
   $ hg up -q 1
   $ mkcommit "B'"
   test-debug-phase: new rev 6:  x -> 1
   created new head
   test-hook-close-phase: cf9fe039dfd67e829edf6522a45de057b5c86519:   -> draft
   $ hglog
   6 1 B'
   5 2 H
   4 2 E
   3 1 D
   2 1 C
   1 0 B
   0 0 A
   $ hg merge 4 # E
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg phase
   6: draft
   4: secret
   $ hg ci -m "merge B' and E"
   test-debug-phase: new rev 7:  x -> 2
   test-hook-close-phase: 17a481b3bccb796c0521ae97903d81c52bfee4af:   -> secret
 
   $ hglog
   7 2 merge B' and E
   6 1 B'
   5 2 H
   4 2 E
   3 1 D
   2 1 C
   1 0 B
   0 0 A
 
 Test secret changeset are not pushed
 
   $ hg init ../push-dest
   $ cat > ../push-dest/.hg/hgrc << EOF
   > [phases]
   > publish=False
   > EOF
   $ hg outgoing ../push-dest --template='{rev} {phase} {desc|firstline}\n'
   comparing with ../push-dest
   searching for changes
   0 public A
   1 public B
   2 draft C
   3 draft D
   6 draft B'
   $ hg outgoing -r 'branch(default)' ../push-dest --template='{rev} {phase} {desc|firstline}\n'
   comparing with ../push-dest
   searching for changes
   0 public A
   1 public B
   2 draft C
   3 draft D
   6 draft B'
 
   $ hg push ../push-dest -f # force because we push multiple heads
   pushing to ../push-dest
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   added 5 changesets with 5 changes to 5 files (+1 heads)
   test-debug-phase: new rev 0:  x -> 0
   test-debug-phase: new rev 1:  x -> 0
   test-debug-phase: new rev 2:  x -> 1
   test-debug-phase: new rev 3:  x -> 1
   test-debug-phase: new rev 4:  x -> 1
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:   -> public
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:   -> public
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:   -> draft
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:   -> draft
   test-hook-close-phase: cf9fe039dfd67e829edf6522a45de057b5c86519:   -> draft
   $ hglog
   7 2 merge B' and E
   6 1 B'
   5 2 H
   4 2 E
   3 1 D
   2 1 C
   1 0 B
   0 0 A
   $ cd ../push-dest
   $ hglog
   4 1 B'
   3 1 D
   2 1 C
   1 0 B
   0 0 A
 
 (Issue3303)
 Check that remote secret changeset are ignore when checking creation of remote heads
 
 We add a secret head into the push destination. This secret head shadows a
 visible shared between the initial repo and the push destination.
 
   $ hg up -q 4 # B'
   $ mkcommit Z --config phases.new-commit=secret
   test-debug-phase: new rev 5:  x -> 2
   test-hook-close-phase: 2713879da13d6eea1ff22b442a5a87cb31a7ce6a:   -> secret
   $ hg phase .
   5: secret
 
 We now try to push a new public changeset that descend from the common public
 head shadowed by the remote secret head.
 
   $ cd ../initialrepo
   $ hg up -q 6 #B'
   $ mkcommit I
   test-debug-phase: new rev 8:  x -> 1
   created new head
   test-hook-close-phase: 6d6770faffce199f1fddd1cf87f6f026138cf061:   -> draft
   $ hg push ../push-dest
   pushing to ../push-dest
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   added 1 changesets with 1 changes to 1 files (+1 heads)
   test-debug-phase: new rev 6:  x -> 1
   test-hook-close-phase: 6d6770faffce199f1fddd1cf87f6f026138cf061:   -> draft
 
 :note: The "(+1 heads)" is wrong as we do not had any visible head
 
 check that branch cache with "served" filter are properly computed and stored
 
   $ ls ../push-dest/.hg/cache/branch2*
   ../push-dest/.hg/cache/branch2-base
   ../push-dest/.hg/cache/branch2-served
   $ cat ../push-dest/.hg/cache/branch2-served
   6d6770faffce199f1fddd1cf87f6f026138cf061 6 465891ffab3c47a3c23792f7dc84156e19a90722
   b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e o default
   6d6770faffce199f1fddd1cf87f6f026138cf061 o default
   $ hg heads -R ../push-dest --template '{rev}:{node} {phase}\n'  #update visible cache too
   6:6d6770faffce199f1fddd1cf87f6f026138cf061 draft
   5:2713879da13d6eea1ff22b442a5a87cb31a7ce6a secret
   3:b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e draft
   $ ls ../push-dest/.hg/cache/branch2*
   ../push-dest/.hg/cache/branch2-base
   ../push-dest/.hg/cache/branch2-served
   ../push-dest/.hg/cache/branch2-visible
   $ cat ../push-dest/.hg/cache/branch2-served
   6d6770faffce199f1fddd1cf87f6f026138cf061 6 465891ffab3c47a3c23792f7dc84156e19a90722
   b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e o default
   6d6770faffce199f1fddd1cf87f6f026138cf061 o default
   $ cat ../push-dest/.hg/cache/branch2-visible
   6d6770faffce199f1fddd1cf87f6f026138cf061 6
   b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e o default
   2713879da13d6eea1ff22b442a5a87cb31a7ce6a o default
   6d6770faffce199f1fddd1cf87f6f026138cf061 o default
 
 
 Restore condition prior extra insertion.
   $ hg -q --config extensions.mq= strip .
   $ hg up -q 7
   $ cd ..
 
 Test secret changeset are not pull
 
   $ hg init pull-dest
   $ cd pull-dest
   $ hg pull ../initialrepo
   pulling from ../initialrepo
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 5 changesets with 5 changes to 5 files (+1 heads)
   new changesets 4a2df7238c3b:cf9fe039dfd6
   test-debug-phase: new rev 0:  x -> 0
   test-debug-phase: new rev 1:  x -> 0
   test-debug-phase: new rev 2:  x -> 0
   test-debug-phase: new rev 3:  x -> 0
   test-debug-phase: new rev 4:  x -> 0
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:   -> public
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:   -> public
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:   -> public
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:   -> public
   test-hook-close-phase: cf9fe039dfd67e829edf6522a45de057b5c86519:   -> public
   (run 'hg heads' to see heads, 'hg merge' to merge)
   $ hglog
   4 0 B'
   3 0 D
   2 0 C
   1 0 B
   0 0 A
   $ cd ..
 
 But secret can still be bundled explicitly
 
   $ cd initialrepo
   $ hg bundle --base '4^' -r 'children(4)' ../secret-bundle.hg
   4 changesets found
   $ cd ..
 
 Test secret changeset are not cloned
 (during local clone)
 
   $ hg clone -qU initialrepo clone-dest
   test-debug-phase: new rev 0:  x -> 0
   test-debug-phase: new rev 1:  x -> 0
   test-debug-phase: new rev 2:  x -> 0
   test-debug-phase: new rev 3:  x -> 0
   test-debug-phase: new rev 4:  x -> 0
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:   -> public
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:   -> public
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:   -> public
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:   -> public
   test-hook-close-phase: cf9fe039dfd67e829edf6522a45de057b5c86519:   -> public
   $ hglog -R clone-dest
   4 0 B'
   3 0 D
   2 0 C
   1 0 B
   0 0 A
 
 Test summary
 
   $ hg summary -R clone-dest --verbose
   parent: -1:000000000000  (no revision checked out)
   branch: default
   commit: (clean)
   update: 5 new changesets (update)
   $ hg summary -R initialrepo
   parent: 7:17a481b3bccb tip
    merge B' and E
   branch: default
   commit: (clean) (secret)
   update: 1 new changesets, 2 branch heads (merge)
   phases: 3 draft, 3 secret
   $ hg summary -R initialrepo --quiet
   parent: 7:17a481b3bccb tip
   update: 1 new changesets, 2 branch heads (merge)
 
 Test revset
 
   $ cd initialrepo
   $ hglog -r 'public()'
   0 0 A
   1 0 B
   $ hglog -r 'draft()'
   2 1 C
   3 1 D
   6 1 B'
   $ hglog -r 'secret()'
   4 2 E
   5 2 H
   7 2 merge B' and E
 
 test that phase are displayed in log at debug level
 
   $ hg log --debug
   changeset:   7:17a481b3bccb796c0521ae97903d81c52bfee4af
   tag:         tip
   phase:       secret
   parent:      6:cf9fe039dfd67e829edf6522a45de057b5c86519
   parent:      4:a603bfb5a83e312131cebcd05353c217d4d21dde
   manifest:    7:5e724ffacba267b2ab726c91fc8b650710deaaa8
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      C D E
   extra:       branch=default
   description:
   merge B' and E
   
   
   changeset:   6:cf9fe039dfd67e829edf6522a45de057b5c86519
   phase:       draft
   parent:      1:27547f69f25460a52fff66ad004e58da7ad3fb56
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    6:ab8bfef2392903058bf4ebb9e7746e8d7026b27a
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      B'
   extra:       branch=default
   description:
   B'
   
   
   changeset:   5:a030c6be5127abc010fcbff1851536552e6951a8
   phase:       secret
   parent:      4:a603bfb5a83e312131cebcd05353c217d4d21dde
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    5:5c710aa854874fe3d5fa7192e77bdb314cc08b5a
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      H
   extra:       branch=default
   description:
   H
   
   
   changeset:   4:a603bfb5a83e312131cebcd05353c217d4d21dde
   phase:       secret
   parent:      3:b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    4:7173fd1c27119750b959e3a0f47ed78abe75d6dc
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      E
   extra:       branch=default
   description:
   E
   
   
   changeset:   3:b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e
   phase:       draft
   parent:      2:f838bfaca5c7226600ebcfd84f3c3c13a28d3757
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    3:6e1f4c47ecb533ffd0c8e52cdc88afb6cd39e20c
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      D
   extra:       branch=default
   description:
   D
   
   
   changeset:   2:f838bfaca5c7226600ebcfd84f3c3c13a28d3757
   phase:       draft
   parent:      1:27547f69f25460a52fff66ad004e58da7ad3fb56
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    2:66a5a01817fdf5239c273802b5b7618d051c89e4
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      C
   extra:       branch=default
   description:
   C
   
   
   changeset:   1:27547f69f25460a52fff66ad004e58da7ad3fb56
   phase:       public
   parent:      0:4a2df7238c3b48766b5e22fafbb8a2f506ec8256
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    1:cb5cbbc1bfbf24cc34b9e8c16914e9caa2d2a7fd
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      B
   extra:       branch=default
   description:
   B
   
   
   changeset:   0:4a2df7238c3b48766b5e22fafbb8a2f506ec8256
   phase:       public
   parent:      -1:0000000000000000000000000000000000000000
   parent:      -1:0000000000000000000000000000000000000000
   manifest:    0:007d8c9d88841325f5c6b06371b35b4e8a2b1a83
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   files+:      A
   extra:       branch=default
   description:
   A
   
   
 
 
 (Issue3707)
 test invalid phase name
 
   $ mkcommit I --config phases.new-commit='babar'
   transaction abort!
   rollback completed
   config error: phases.new-commit: not a valid phase name ('babar')
   [30]
 Test phase command
 ===================
 
 initial picture
 
   $ hg log -G --template "{rev} {phase} {desc}\n"
   @    7 secret merge B' and E
   |\
   | o  6 draft B'
   | |
   +---o  5 secret H
   | |
   o |  4 secret E
   | |
   o |  3 draft D
   | |
   o |  2 draft C
   |/
   o  1 public B
   |
   o  0 public A
   
 
 display changesets phase
 
 (mixing -r and plain rev specification)
 
   $ hg phase 1::4 -r 7
   1: public
   2: draft
   3: draft
   4: secret
   7: secret
 
 
 move changeset forward
 
 (with -r option)
 
   $ hg phase --public -r 2
   test-debug-phase: move rev 2: 1 -> 0
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:  draft -> public
   $ hg log -G --template "{rev} {phase} {desc}\n"
   @    7 secret merge B' and E
   |\
   | o  6 draft B'
   | |
   +---o  5 secret H
   | |
   o |  4 secret E
   | |
   o |  3 draft D
   | |
   o |  2 public C
   |/
   o  1 public B
   |
   o  0 public A
   
 
 move changeset backward
 
 (without -r option)
 
   $ hg phase --draft --force 2
   test-debug-phase: move rev 2: 0 -> 1
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:  public -> draft
   $ hg log -G --template "{rev} {phase} {desc}\n"
   @    7 secret merge B' and E
   |\
   | o  6 draft B'
   | |
   +---o  5 secret H
   | |
   o |  4 secret E
   | |
   o |  3 draft D
   | |
   o |  2 draft C
   |/
   o  1 public B
   |
   o  0 public A
   
 
 move changeset forward and backward
 
   $ hg phase --draft --force 1::4
   test-debug-phase: move rev 1: 0 -> 1
   test-debug-phase: move rev 4: 2 -> 1
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:  public -> draft
   test-hook-close-phase: a603bfb5a83e312131cebcd05353c217d4d21dde:  secret -> draft
   $ hg log -G --template "{rev} {phase} {desc}\n"
   @    7 secret merge B' and E
   |\
   | o  6 draft B'
   | |
   +---o  5 secret H
   | |
   o |  4 draft E
   | |
   o |  3 draft D
   | |
   o |  2 draft C
   |/
   o  1 draft B
   |
   o  0 public A
   
 test partial failure
 
   $ hg phase --public 7
   test-debug-phase: move rev 1: 1 -> 0
   test-debug-phase: move rev 2: 1 -> 0
   test-debug-phase: move rev 3: 1 -> 0
   test-debug-phase: move rev 4: 1 -> 0
   test-debug-phase: move rev 6: 1 -> 0
   test-debug-phase: move rev 7: 2 -> 0
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:  draft -> public
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:  draft -> public
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:  draft -> public
   test-hook-close-phase: a603bfb5a83e312131cebcd05353c217d4d21dde:  draft -> public
   test-hook-close-phase: cf9fe039dfd67e829edf6522a45de057b5c86519:  draft -> public
   test-hook-close-phase: 17a481b3bccb796c0521ae97903d81c52bfee4af:  secret -> public
   $ hg phase --draft '5 or 7'
   test-debug-phase: move rev 5: 2 -> 1
   test-hook-close-phase: a030c6be5127abc010fcbff1851536552e6951a8:  secret -> draft
   cannot move 1 changesets to a higher phase, use --force
   phase changed for 1 changesets
   [1]
   $ hg log -G --template "{rev} {phase} {desc}\n"
   @    7 public merge B' and E
   |\
   | o  6 public B'
   | |
   +---o  5 draft H
   | |
   o |  4 public E
   | |
   o |  3 public D
   | |
   o |  2 public C
   |/
   o  1 public B
   |
   o  0 public A
   
 
 test complete failure
 
   $ hg phase --draft 7
   cannot move 1 changesets to a higher phase, use --force
   no phases changed
   [1]
 
   $ cd ..
 
 test hidden changeset are not cloned as public (issue3935)
 
   $ cd initialrepo
 
 (enabling evolution)
   $ cat >> $HGRCPATH << EOF
   > [experimental]
   > evolution.createmarkers=True
   > EOF
 
 (making a changeset hidden; H in that case)
   $ hg debugobsolete `hg id --debug -r 5`
   1 new obsolescence markers
   obsoleted 1 changesets
 
   $ cd ..
   $ hg clone initialrepo clonewithobs
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 7 changesets with 6 changes to 6 files
   new changesets 4a2df7238c3b:17a481b3bccb
   test-debug-phase: new rev 0:  x -> 0
   test-debug-phase: new rev 1:  x -> 0
   test-debug-phase: new rev 2:  x -> 0
   test-debug-phase: new rev 3:  x -> 0
   test-debug-phase: new rev 4:  x -> 0
   test-debug-phase: new rev 5:  x -> 0
   test-debug-phase: new rev 6:  x -> 0
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:   -> public
   test-hook-close-phase: 27547f69f25460a52fff66ad004e58da7ad3fb56:   -> public
   test-hook-close-phase: f838bfaca5c7226600ebcfd84f3c3c13a28d3757:   -> public
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:   -> public
   test-hook-close-phase: a603bfb5a83e312131cebcd05353c217d4d21dde:   -> public
   test-hook-close-phase: cf9fe039dfd67e829edf6522a45de057b5c86519:   -> public
   test-hook-close-phase: 17a481b3bccb796c0521ae97903d81c52bfee4af:   -> public
   updating to branch default
   6 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd clonewithobs
   $ hg log -G --template "{rev} {phase} {desc}\n"
   @    6 public merge B' and E
   |\
   | o  5 public B'
   | |
   o |  4 public E
   | |
   o |  3 public D
   | |
   o |  2 public C
   |/
   o  1 public B
   |
   o  0 public A
   
 
 test verify repo containing hidden changesets, which should not abort just
 because repo.cancopy() is False
 
   $ cd ../initialrepo
   $ hg verify
   checking changesets
   checking manifests
   crosschecking files in changesets and manifests
   checking files
   checked 8 changesets with 7 changes to 7 files
 
   $ cd ..
 
 check whether HG_PENDING makes pending changes only in related
 repositories visible to an external hook.
 
 (emulate a transaction running concurrently by copied
 .hg/phaseroots.pending in subsequent test)
 
   $ cat > $TESTTMP/savepending.sh <<EOF
   > cp .hg/store/phaseroots.pending  .hg/store/phaseroots.pending.saved
   > exit 1 # to avoid changing phase for subsequent tests
   > EOF
   $ cd push-dest
   $ hg phase 6
   6: draft
   $ hg --config hooks.pretxnclose="sh $TESTTMP/savepending.sh" phase -f -s 6
   transaction abort!
   rollback completed
   abort: pretxnclose hook exited with status 1
   [40]
   $ cp .hg/store/phaseroots.pending.saved .hg/store/phaseroots.pending
 
 (check (in)visibility of phaseroot while transaction running in repo)
 
   $ cat > $TESTTMP/checkpending.sh <<EOF
   > echo '@initialrepo'
   > hg -R "$TESTTMP/initialrepo" phase 7
   > echo '@push-dest'
   > hg -R "$TESTTMP/push-dest" phase 6
   > exit 1 # to avoid changing phase for subsequent tests
   > EOF
   $ cd ../initialrepo
   $ hg phase 7
   7: public
   $ hg --config hooks.pretxnclose="sh $TESTTMP/checkpending.sh" phase -f -s 7
   @initialrepo
   7: secret
   @push-dest
   6: draft
   transaction abort!
   rollback completed
   abort: pretxnclose hook exited with status 1
   [40]
 
 Check that pretxnclose-phase hook can control phase movement
 
   $ hg phase --force b3325c91a4d9 --secret
   test-debug-phase: move rev 3: 0 -> 2
   test-debug-phase: move rev 4: 0 -> 2
   test-debug-phase: move rev 5: 1 -> 2
   test-debug-phase: move rev 7: 0 -> 2
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:  public -> secret
   test-hook-close-phase: a603bfb5a83e312131cebcd05353c217d4d21dde:  public -> secret
   test-hook-close-phase: a030c6be5127abc010fcbff1851536552e6951a8:  draft -> secret
   test-hook-close-phase: 17a481b3bccb796c0521ae97903d81c52bfee4af:  public -> secret
   $ hg log -G -T phases
   @    changeset:   7:17a481b3bccb
   |\   tag:         tip
   | |  phase:       secret
   | |  parent:      6:cf9fe039dfd6
   | |  parent:      4:a603bfb5a83e
   | |  user:        test
   | |  date:        Thu Jan 01 00:00:00 1970 +0000
   | |  summary:     merge B' and E
   | |
   | o  changeset:   6:cf9fe039dfd6
   | |  phase:       public
   | |  parent:      1:27547f69f254
   | |  user:        test
   | |  date:        Thu Jan 01 00:00:00 1970 +0000
   | |  summary:     B'
   | |
   o |  changeset:   4:a603bfb5a83e
   | |  phase:       secret
   | |  user:        test
   | |  date:        Thu Jan 01 00:00:00 1970 +0000
   | |  summary:     E
   | |
   o |  changeset:   3:b3325c91a4d9
   | |  phase:       secret
   | |  user:        test
   | |  date:        Thu Jan 01 00:00:00 1970 +0000
   | |  summary:     D
   | |
   o |  changeset:   2:f838bfaca5c7
   |/   phase:       public
   |    user:        test
   |    date:        Thu Jan 01 00:00:00 1970 +0000
   |    summary:     C
   |
   o  changeset:   1:27547f69f254
   |  phase:       public
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     B
   |
   o  changeset:   0:4a2df7238c3b
      phase:       public
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     A
   
 
 Install a hook that prevent b3325c91a4d9 to become public
 
   $ cat >> .hg/hgrc << EOF
   > [hooks]
   > pretxnclose-phase.nopublish_D = sh -c "(echo \$HG_NODE| grep -v b3325c91a4d9>/dev/null) || [ 'public' != \$HG_PHASE ]"
   > EOF
 
 Try various actions. only the draft move should succeed
 
   $ hg phase --public b3325c91a4d9
   transaction abort!
   rollback completed
   abort: pretxnclose-phase.nopublish_D hook exited with status 1
   [40]
   $ hg phase --public a603bfb5a83e
   transaction abort!
   rollback completed
   abort: pretxnclose-phase.nopublish_D hook exited with status 1
   [40]
   $ hg phase --draft 17a481b3bccb
   test-debug-phase: move rev 3: 2 -> 1
   test-debug-phase: move rev 4: 2 -> 1
   test-debug-phase: move rev 7: 2 -> 1
   test-hook-close-phase: b3325c91a4d916bcc4cdc83ea3fe4ece46a42f6e:  secret -> draft
   test-hook-close-phase: a603bfb5a83e312131cebcd05353c217d4d21dde:  secret -> draft
   test-hook-close-phase: 17a481b3bccb796c0521ae97903d81c52bfee4af:  secret -> draft
   $ hg phase --public 17a481b3bccb
   transaction abort!
   rollback completed
   abort: pretxnclose-phase.nopublish_D hook exited with status 1
   [40]
 
   $ cd ..
 
 Test for the "internal" phase
 =============================
 
 Check we deny its usage on older repository
 
   $ hg init no-internal-phase --config format.internal-phase=no
   $ cd no-internal-phase
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   $ echo X > X
   $ hg add X
   $ hg status
   A X
   $ hg --config "phases.new-commit=internal" commit -m "my test internal commit" 2>&1 | grep ProgrammingError
   ** ProgrammingError: this repository does not support the internal phase
       raise error.ProgrammingError(msg) (no-pyoxidizer !)
   *ProgrammingError: this repository does not support the internal phase (glob)
   $ hg --config "phases.new-commit=archived" commit -m "my test archived commit" 2>&1 | grep ProgrammingError
   ** ProgrammingError: this repository does not support the archived phase
       raise error.ProgrammingError(msg) (no-pyoxidizer !)
   *ProgrammingError: this repository does not support the archived phase (glob)
 
   $ cd ..
 
 Check it works fine with repository that supports it.
 
   $ hg init internal-phase --config format.internal-phase=yes
   $ cd internal-phase
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   internal-phase
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   $ mkcommit A
   test-debug-phase: new rev 0:  x -> 1
   test-hook-close-phase: 4a2df7238c3b48766b5e22fafbb8a2f506ec8256:   -> draft
 
 Commit an internal changesets
 
   $ echo B > B
   $ hg add B
   $ hg status
   A B
   $ hg --config "phases.new-commit=internal" commit -m "my test internal commit"
   test-debug-phase: new rev 1:  x -> 96
   test-hook-close-phase: c01c42dffc7f81223397e99652a0703f83e1c5ea:   -> internal
 
 The changeset is a working parent descendant.
 Per the usual visibility rules, it is made visible.
 
   $ hg log -G -l 3
   @  changeset:   1:c01c42dffc7f
   |  tag:         tip
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     my test internal commit
   |
   o  changeset:   0:4a2df7238c3b
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     A
   
 
 Commit is hidden as expected
 
   $ hg up 0
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg log -G
   @  changeset:   0:4a2df7238c3b
      tag:         tip
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     A
   
 
 Test for archived phase
 -----------------------
 
 Commit an archived changesets
 
   $ echo B > B
   $ hg add B
   $ hg status
   A B
   $ hg --config "phases.new-commit=archived" commit -m "my test archived commit"
   test-debug-phase: new rev 2:  x -> 32
   test-hook-close-phase: 8df5997c3361518f733d1ae67cd3adb9b0eaf125:   -> archived
 
 The changeset is a working parent descendant.
 Per the usual visibility rules, it is made visible.
 
   $ hg log -G -l 3
   @  changeset:   2:8df5997c3361
   |  tag:         tip
   |  parent:      0:4a2df7238c3b
   |  user:        test
   |  date:        Thu Jan 01 00:00:00 1970 +0000
   |  summary:     my test archived commit
   |
   o  changeset:   0:4a2df7238c3b
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     A
   
 
 Commit is hidden as expected
 
   $ hg up 0
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg log -G
   @  changeset:   0:4a2df7238c3b
      tag:         tip
      user:        test
      date:        Thu Jan 01 00:00:00 1970 +0000
      summary:     A
   
   $ cd ..
 
 Recommitting an exact match of a public commit shouldn't change it to
 draft:
 
   $ cd initialrepo
   $ hg phase -r 2
   2: public
   $ hg up -C 1
   0 files updated, 0 files merged, 4 files removed, 0 files unresolved
   $ mkcommit C
   warning: commit already existed in the repository!
   $ hg phase -r 2
   2: public
 
 Same, but for secret:
 
   $ hg up 7
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ mkcommit F -s
   test-debug-phase: new rev 8:  x -> 2
   test-hook-close-phase: de414268ec5ce2330c590b942fbb5ff0b0ca1a0a:   -> secret
   $ hg up 7
   0 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ hg phase
   7: draft
   $ mkcommit F
   test-debug-phase: new rev 8:  x -> 2
   warning: commit already existed in the repository!
   test-hook-close-phase: de414268ec5ce2330c590b942fbb5ff0b0ca1a0a:   -> secret
   $ hg phase -r tip
   8: secret
 
 But what about obsoleted changesets?
 
   $ hg up 4
   0 files updated, 0 files merged, 2 files removed, 0 files unresolved
   $ mkcommit H
   test-debug-phase: new rev 5:  x -> 2
   warning: commit already existed in the repository!
   test-hook-close-phase: a030c6be5127abc010fcbff1851536552e6951a8:   -> secret
   $ hg phase -r 5
   5: secret
   $ hg par
   changeset:   5:a030c6be5127
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   obsolete:    pruned
   summary:     H
   
   $ hg up tip
   2 files updated, 0 files merged, 1 files removed, 0 files unresolved
   $ cd ..

tests/test-remotefilelog-clone-tree.t

@@ -1,127 +1,127 b''
 #require no-windows
 
   $ . "$TESTDIR/remotefilelog-library.sh"
 
   $ hg init master
   $ cd master
   $ echo treemanifest >> .hg/requires
   $ cat >> .hg/hgrc <<EOF
   > [remotefilelog]
   > server=True
   > EOF
 # uppercase directory name to test encoding
   $ mkdir -p A/B
   $ echo x > A/B/x
   $ hg commit -qAm x
 
   $ cd ..
 
 # shallow clone from full
 
   $ hgcloneshallow ssh://user@dummy/master shallow --noupdate
   streaming all changes
   4 files to transfer, 449 bytes of data
   transferred 449 bytes in * seconds (*/sec) (glob)
   searching for changes
   no changes found
   $ cd shallow
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   treemanifest
   $ find .hg/store/meta | sort
   .hg/store/meta
   .hg/store/meta/_a
   .hg/store/meta/_a/00manifest.i
   .hg/store/meta/_a/_b
   .hg/store/meta/_a/_b/00manifest.i
 
   $ hg update
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   1 files fetched over 1 fetches - (1 misses, 0.00% hit ratio) over *s (glob)
 
   $ cat A/B/x
   x
 
   $ ls .hg/store/data
   $ echo foo > A/B/F
   $ hg add A/B/F
   $ hg ci -m 'local content'
   $ ls .hg/store/data
   ca31988f085bfb945cb8115b78fabdee40f741aa
 
   $ cd ..
 
 # shallow clone from shallow
 
   $ hgcloneshallow ssh://user@dummy/shallow shallow2  --noupdate
   streaming all changes
   5 files to transfer, 1008 bytes of data
   transferred 1008 bytes in * seconds (*/sec) (glob)
   searching for changes
   no changes found
   $ cd shallow2
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   treemanifest
   $ ls .hg/store/data
   ca31988f085bfb945cb8115b78fabdee40f741aa
 
   $ hg update
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ cat A/B/x
   x
 
   $ cd ..
 
 # full clone from shallow
 # - send stderr to /dev/null because the order of stdout/err causes
 #   flakiness here
   $ hg clone --noupdate ssh://user@dummy/shallow full 2>/dev/null
   streaming all changes
   [100]
 
 # getbundle full clone
 
   $ printf '[server]\npreferuncompressed=False\n' >> master/.hg/hgrc
   $ hgcloneshallow ssh://user@dummy/master shallow3
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 1 changesets with 0 changes to 0 files
   new changesets 18d955ee7ba0
   updating to branch default
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ ls shallow3/.hg/store/data
   $ cat shallow3/.hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   treemanifest

tests/test-remotefilelog-clone.t

@@ -1,124 +1,124 b''
 #require no-windows
 
   $ . "$TESTDIR/remotefilelog-library.sh"
 
   $ hg init master
   $ cd master
   $ cat >> .hg/hgrc <<EOF
   > [remotefilelog]
   > server=True
   > EOF
   $ echo x > x
   $ hg commit -qAm x
 
   $ cd ..
 
 # shallow clone from full
 
   $ hgcloneshallow ssh://user@dummy/master shallow --noupdate
   streaming all changes
   2 files to transfer, 227 bytes of data
   transferred 227 bytes in * seconds (*/sec) (glob)
   searching for changes
   no changes found
   $ cd shallow
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
   $ hg update
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   1 files fetched over 1 fetches - (1 misses, 0.00% hit ratio) over *s (glob)
 
   $ cat x
   x
 
   $ ls .hg/store/data
   $ echo foo > f
   $ hg add f
   $ hg ci -m 'local content'
   $ ls .hg/store/data
   4a0a19218e082a343a1b17e5333409af9d98f0f5
 
   $ cd ..
 
 # shallow clone from shallow
 
   $ hgcloneshallow ssh://user@dummy/shallow shallow2  --noupdate
   streaming all changes
   3 files to transfer, 564 bytes of data
   transferred 564 bytes in * seconds (*/sec) (glob)
   searching for changes
   no changes found
   $ cd shallow2
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   $ ls .hg/store/data
   4a0a19218e082a343a1b17e5333409af9d98f0f5
 
   $ hg update
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ cat x
   x
 
   $ cd ..
 
 # full clone from shallow
 
 Note: the output to STDERR comes from a different process to the output on
 STDOUT and their relative ordering is not deterministic. As a result, the test
 was failing sporadically. To avoid this, we capture STDERR to a file and
 check its contents separately.
 
   $ TEMP_STDERR=full-clone-from-shallow.stderr.tmp
   $ hg clone --noupdate ssh://user@dummy/shallow full 2>$TEMP_STDERR
   streaming all changes
   [100]
   $ cat $TEMP_STDERR
   remote: abort: Cannot clone from a shallow repo to a full repo.
   abort: pull failed on remote
   $ rm $TEMP_STDERR
 
 # getbundle full clone
 
   $ printf '[server]\npreferuncompressed=False\n' >> master/.hg/hgrc
   $ hgcloneshallow ssh://user@dummy/master shallow3
   requesting all changes
   adding changesets
   adding manifests
   adding file changes
   added 1 changesets with 0 changes to 0 files
   new changesets b292c1e3311f
   updating to branch default
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ ls shallow3/.hg/store/data
   $ cat shallow3/.hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store

tests/test-remotefilelog-log.t

@@ -1,121 +1,121 b''
 #require no-windows
 
   $ . "$TESTDIR/remotefilelog-library.sh"
 
   $ hg init master
   $ cd master
   $ cat >> .hg/hgrc <<EOF
   > [remotefilelog]
   > server=True
   > EOF
   $ echo x > x
   $ hg commit -qAm x
   $ mkdir dir
   $ echo y > dir/y
   $ hg commit -qAm y
 
   $ cd ..
 
 Shallow clone from full
 
   $ hgcloneshallow ssh://user@dummy/master shallow --noupdate
   streaming all changes
   2 files to transfer, 473 bytes of data
   transferred 473 bytes in * seconds (*/sec) (glob)
   searching for changes
   no changes found
   $ cd shallow
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-remotefilelog-repo-req-1
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
   $ hg update
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   2 files fetched over 1 fetches - (2 misses, 0.00% hit ratio) over *s (glob)
 
 Log on a file without -f
 
   $ hg log dir/y
   warning: file log can be slow on large repos - use -f to speed it up
   changeset:   1:2e73264fab97
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     y
   
 Log on a file with -f
 
   $ hg log -f dir/y
   changeset:   1:2e73264fab97
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     y
   
 Log on a file with kind in path
   $ hg log -r "filelog('path:dir/y')"
   changeset:   1:2e73264fab97
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     y
   
 Log on multiple files with -f
 
   $ hg log -f dir/y x
   changeset:   1:2e73264fab97
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     y
   
   changeset:   0:b292c1e3311f
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     x
   
 Log on a directory
 
   $ hg log dir
   changeset:   1:2e73264fab97
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     y
   
 Log on a file from inside a directory
 
   $ cd dir
   $ hg log y
   warning: file log can be slow on large repos - use -f to speed it up
   changeset:   1:2e73264fab97
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     y
   
 Log on a file via -fr
   $ cd ..
   $ hg log -fr tip dir/ --template '{rev}\n'
   1
 
 Trace renames
   $ hg mv x z
   $ hg commit -m move
   $ hg log -f z -T '{desc} {file_copies}\n' -G
   @  move z (x)
   :
   o  x
   
 
 Verify remotefilelog handles rename metadata stripping when comparing file sizes
   $ hg debugrebuilddirstate
   $ hg status

tests/test-repo-compengines.t

@@ -1,258 +1,258 b''
 A new repository uses zlib storage, which doesn't need a requirement
 
   $ cat << EOF >> $HGRCPATH
   > [format]
   > # stabilize test accross variant
   > revlog-compression=zlib
   > EOF
 
 
   $ hg init default
   $ cd default
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ touch foo
   $ hg -q commit -A -m 'initial commit with a lot of repeated repeated repeated text to trigger compression'
   $ hg debugrevlog -c | grep 0x78
       0x78 (x)  :   1 (100.00%)
       0x78 (x)  : 110 (100.00%)
 
   $ cd ..
 
 Unknown compression engine to format.compression aborts
 
   $ hg --config format.revlog-compression=unknown init unknown
   abort: compression engines "unknown" defined by format.revlog-compression not available
   (run "hg debuginstall" to list available compression engines)
   [255]
 
 unknown compression engine in a list with known one works fine
 
   $ hg --config format.revlog-compression=zlib,unknown init zlib-before-unknow
   $ hg --config format.revlog-compression=unknown,zlib init unknown-before-zlib
 
 A requirement specifying an unknown compression engine results in bail
 
   $ hg init unknownrequirement
   $ cd unknownrequirement
   $ echo exp-compression-unknown >> .hg/requires
   $ hg log
   abort: repository requires features unknown to this Mercurial: exp-compression-unknown
   (see https://mercurial-scm.org/wiki/MissingRequirement for more information)
   [255]
 
   $ cd ..
 
 Specifying a new format.compression on an existing repo won't introduce data
 with that engine or a requirement
 
   $ cd default
   $ touch bar
   $ hg --config format.revlog-compression=none -q commit -A -m 'add bar with a lot of repeated repeated repeated text'
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ hg debugrevlog -c | grep 0x78
       0x78 (x)  :   2 (100.00%)
       0x78 (x)  : 199 (100.00%)
   $ cd ..
 
 #if zstd
 
   $ hg --config format.revlog-compression=zstd init zstd
   $ cd zstd
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ touch foo
   $ hg -q commit -A -m 'initial commit with a lot of repeated repeated repeated text'
 
   $ hg debugrevlog -c | grep 0x28
       0x28      :  1 (100.00%)
       0x28      : 98 (100.00%)
 
   $ cd ..
 
 
 #endif
 
 checking zlib options
 =====================
 
   $ hg init zlib-level-default
   $ hg init zlib-level-1
   $ cat << EOF >> zlib-level-1/.hg/hgrc
   > [storage]
   > revlog.zlib.level=1
   > EOF
   $ hg init zlib-level-9
   $ cat << EOF >> zlib-level-9/.hg/hgrc
   > [storage]
   > revlog.zlib.level=9
   > EOF
 
 
   $ commitone() {
   >    repo=$1
   >    cp $RUNTESTDIR/bundles/issue4438-r1.hg $repo/a
   >    hg -R $repo add $repo/a
   >    hg -R $repo commit -m some-commit
   > }
 
   $ for repo in zlib-level-default zlib-level-1 zlib-level-9; do
   >     commitone $repo
   > done
 
   $ $RUNTESTDIR/f -s */.hg/store/data/*
   default/.hg/store/data/bar.i: size=64
   default/.hg/store/data/foo.i: size=64
   zlib-level-1/.hg/store/data/a.i: size=4146
   zlib-level-9/.hg/store/data/a.i: size=4138
   zlib-level-default/.hg/store/data/a.i: size=4138
   zstd/.hg/store/data/foo.i: size=64 (zstd !)
 
 Test error cases
 
   $ hg init zlib-level-invalid
   $ cat << EOF >> zlib-level-invalid/.hg/hgrc
   > [storage]
   > revlog.zlib.level=foobar
   > EOF
   $ commitone zlib-level-invalid
   config error: storage.revlog.zlib.level is not a valid integer ('foobar')
   config error: storage.revlog.zlib.level is not a valid integer ('foobar')
   [30]
 
   $ hg init zlib-level-out-of-range
   $ cat << EOF >> zlib-level-out-of-range/.hg/hgrc
   > [storage]
   > revlog.zlib.level=42
   > EOF
 
   $ commitone zlib-level-out-of-range
   abort: invalid value for `storage.revlog.zlib.level` config: 42
   abort: invalid value for `storage.revlog.zlib.level` config: 42
   [255]
 
 checking details of none compression
 ====================================
 
   $ hg init none-compression --config format.revlog-compression=none
 
   $ commitone() {
   >    repo=$1
   >    cp $RUNTESTDIR/bundles/issue4438-r1.hg $repo/a
   >    hg -R $repo add $repo/a
   >    hg -R $repo commit -m some-commit
   > }
 
   $ commitone none-compression
 
   $ hg log -R none-compression
   changeset:   0:68b53da39cd8
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     some-commit
   
 
   $ cat none-compression/.hg/requires
   dotencode
   exp-compression-none
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ $RUNTESTDIR/f -s none-compression/.hg/store/data/*
   none-compression/.hg/store/data/a.i: size=4216
 
 #if zstd
 
 checking zstd options
 =====================
 
   $ hg init zstd-level-default --config format.revlog-compression=zstd
   $ hg init zstd-level-1 --config format.revlog-compression=zstd
   $ cat << EOF >> zstd-level-1/.hg/hgrc
   > [storage]
   > revlog.zstd.level=1
   > EOF
   $ hg init zstd-level-22 --config format.revlog-compression=zstd
   $ cat << EOF >> zstd-level-22/.hg/hgrc
   > [storage]
   > revlog.zstd.level=22
   > EOF
 
 
   $ commitone() {
   >    repo=$1
   >    cp $RUNTESTDIR/bundles/issue4438-r1.hg $repo/a
   >    hg -R $repo add $repo/a
   >    hg -R $repo commit -m some-commit
   > }
 
   $ for repo in zstd-level-default zstd-level-1 zstd-level-22; do
   >     commitone $repo
   > done
 
   $ $RUNTESTDIR/f -s zstd-*/.hg/store/data/*
   zstd-level-1/.hg/store/data/a.i: size=4114
   zstd-level-22/.hg/store/data/a.i: size=4091
   zstd-level-default/\.hg/store/data/a\.i: size=(4094|4102) (re)
 
 Test error cases
 
   $ hg init zstd-level-invalid --config format.revlog-compression=zstd
   $ cat << EOF >> zstd-level-invalid/.hg/hgrc
   > [storage]
   > revlog.zstd.level=foobar
   > EOF
   $ commitone zstd-level-invalid
   config error: storage.revlog.zstd.level is not a valid integer ('foobar')
   config error: storage.revlog.zstd.level is not a valid integer ('foobar')
   [30]
 
   $ hg init zstd-level-out-of-range --config format.revlog-compression=zstd
   $ cat << EOF >> zstd-level-out-of-range/.hg/hgrc
   > [storage]
   > revlog.zstd.level=42
   > EOF
 
   $ commitone zstd-level-out-of-range
   abort: invalid value for `storage.revlog.zstd.level` config: 42
   abort: invalid value for `storage.revlog.zstd.level` config: 42
   [255]
 
 #endif

tests/test-requires.t

@@ -1,84 +1,84 b''
   $ hg init t
   $ cd t
   $ echo a > a
   $ hg add a
   $ hg commit -m test
   $ rm .hg/requires
   $ hg tip
   abort: unknown version (65535) in revlog 00changelog
   [50]
   $ echo indoor-pool > .hg/requires
   $ hg tip
   abort: repository requires features unknown to this Mercurial: indoor-pool
   (see https://mercurial-scm.org/wiki/MissingRequirement for more information)
   [255]
   $ echo outdoor-pool >> .hg/requires
   $ hg tip
   abort: repository requires features unknown to this Mercurial: indoor-pool outdoor-pool
   (see https://mercurial-scm.org/wiki/MissingRequirement for more information)
   [255]
   $ cd ..
 
 Test checking between features supported locally and ones required in
 another repository of push/pull/clone on localhost:
 
   $ mkdir supported-locally
   $ cd supported-locally
 
   $ hg init supported
   $ echo a > supported/a
   $ hg -R supported commit -Am '#0 at supported'
   adding a
 
   $ echo 'featuresetup-test' >> supported/.hg/requires
   $ cat > $TESTTMP/supported-locally/supportlocally.py <<EOF
   > from __future__ import absolute_import
   > from mercurial import extensions, localrepo
   > def featuresetup(ui, supported):
   >     for name, module in extensions.extensions(ui):
   >         if __name__ == module.__name__:
   >             # support specific feature locally
   >             supported |= {b'featuresetup-test'}
   >             return
   > def uisetup(ui):
   >     localrepo.featuresetupfuncs.add(featuresetup)
   > EOF
   $ cat > supported/.hg/hgrc <<EOF
   > [extensions]
   > # enable extension locally
   > supportlocally = $TESTTMP/supported-locally/supportlocally.py
   > EOF
   $ hg -R supported debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   featuresetup-test
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   $ hg -R supported status
 
   $ hg init push-dst
   $ hg -R supported push push-dst
   pushing to push-dst
   abort: required features are not supported in the destination: featuresetup-test
   [255]
 
   $ hg init pull-src
   $ hg -R pull-src pull supported
   pulling from supported
   abort: required features are not supported in the destination: featuresetup-test
   [255]
 
   $ hg clone supported clone-dst
   abort: repository requires features unknown to this Mercurial: featuresetup-test
   (see https://mercurial-scm.org/wiki/MissingRequirement for more information)
   [255]
   $ hg clone --pull supported clone-dst
   abort: required features are not supported in the destination: featuresetup-test
   [255]
 
   $ cd ..

tests/test-revlog-v2.t

@@ -1,139 +1,139 b''
 #require reporevlogstore
 
 A repo with unknown revlogv2 requirement string cannot be opened
 
   $ hg init invalidreq
   $ cd invalidreq
   $ echo exp-revlogv2.unknown >> .hg/requires
   $ hg log
   abort: repository requires features unknown to this Mercurial: exp-revlogv2.unknown
   (see https://mercurial-scm.org/wiki/MissingRequirement for more information)
   [255]
   $ cd ..
 
 Can create and open repo with revlog v2 requirement
 
   $ cat >> $HGRCPATH << EOF
   > [experimental]
   > revlogv2 = enable-unstable-format-and-corrupt-my-data
   > EOF
 
   $ hg init new-repo
   $ cd new-repo
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-revlogv2.2
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   sparserevlog
   store
 
   $ hg log
 
 Unknown flags to revlog are rejected
 
   >>> with open('.hg/store/00changelog.i', 'wb') as fh:
   ...     fh.write(b'\xff\x00\xde\xad') and None
 
   $ hg log
   abort: unknown flags (0xff00) in version 57005 revlog 00changelog
   [50]
 
   $ cd ..
 
 Writing a simple revlog v2 works
 
   $ hg init simple
   $ cd simple
   $ touch foo
   $ hg -q commit -A -m initial
 
   $ hg log
   changeset:   0:96ee1d7354c4
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     initial
   
 
 Header written as expected
 
   $ f --hexdump --bytes 4 .hg/store/00changelog.i
   .hg/store/00changelog.i:
   0000: 00 00 de ad                                     |....|
 
   $ f --hexdump --bytes 4 .hg/store/data/foo.i
   .hg/store/data/foo.i:
   0000: 00 00 de ad                                     |....|
 
 Bundle use a compatible changegroup format
 ------------------------------------------
 
   $ hg bundle --all ../basic.hg
   1 changesets found
   $ hg debugbundle --spec ../basic.hg
   bzip2-v2
 
 The expected files are generated
 --------------------------------
 
 We should have have:
 - a docket
 - a index file with a unique name
 - a data file
 
   $ ls .hg/store/00changelog* .hg/store/00manifest*
   .hg/store/00changelog-1335303a.sda
   .hg/store/00changelog-6b8ab34b.idx
   .hg/store/00changelog-b875dfc5.dat
   .hg/store/00changelog.i
   .hg/store/00manifest-05a21d65.idx
   .hg/store/00manifest-43c37dde.dat
   .hg/store/00manifest-e2c9362a.sda
   .hg/store/00manifest.i
 
 Local clone works
 -----------------
 
   $ hg clone . ../cloned-repo
   updating to branch default
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg tip | tee ../tip-new
   changeset:   0:96ee1d7354c4
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     initial
   
   $ hg tip -R ../cloned-repo | tee ../tip-cloned
   changeset:   0:96ee1d7354c4
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     initial
   
 
 The two repository should be identical, this diff MUST be empty
 
   $ cmp ../tip-new ../tip-cloned || diff -U8 ../tip-new ../tip-cloned
 
 
 hg verify should be happy
 -------------------------
 
   $ hg verify
   checking changesets
   checking manifests
   crosschecking files in changesets and manifests
   checking files
   checked 1 changesets with 1 changes to 1 files
 
   $ hg verify -R ../cloned-repo
   checking changesets
   checking manifests
   crosschecking files in changesets and manifests
   checking files
   checked 1 changesets with 1 changes to 1 files

tests/test-share-safe.t

@@ -1,619 +1,619 b''
 setup
 
   $ cat >> $HGRCPATH <<EOF
   > [extensions]
   > share =
   > [format]
   > use-share-safe = True
   > [storage]
   > revlog.persistent-nodemap.slow-path=allow
   > # enforce zlib to ensure we can upgrade to zstd later
   > [format]
   > revlog-compression=zlib
   > # we want to be able to enable it later
   > use-persistent-nodemap=no
   > EOF
 
 prepare source repo
 
   $ hg init source
   $ cd source
   $ cat .hg/requires
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   share-safe
   $ cat .hg/store/requires
   dotencode
   fncache
   generaldelta
   revlogv1
   sparserevlog
   store
   $ hg debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   share-safe
   sparserevlog
   store
 
   $ echo a > a
   $ hg ci -Aqm "added a"
   $ echo b > b
   $ hg ci -Aqm "added b"
 
   $ HGEDITOR=cat hg config --shared
   abort: repository is not shared; can't use --shared
   [10]
   $ cd ..
 
 Create a shared repo and check the requirements are shared and read correctly
   $ hg share source shared1
   updating working directory
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd shared1
   $ cat .hg/requires
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   share-safe
   shared
 
   $ hg debugrequirements -R ../source
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   share-safe
   sparserevlog
   store
 
   $ hg debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   share-safe
   shared
   sparserevlog
   store
 
   $ echo c > c
   $ hg ci -Aqm "added c"
 
 Check that config of the source repository is also loaded
 
   $ hg showconfig ui.curses
   [1]
 
   $ echo "[ui]" >> ../source/.hg/hgrc
   $ echo "curses=true" >> ../source/.hg/hgrc
 
   $ hg showconfig ui.curses
   true
 
 Test that extensions of source repository are also loaded
 
   $ hg debugextensions
   share
   $ hg extdiff -p echo
   hg: unknown command 'extdiff'
   'extdiff' is provided by the following extension:
   
       extdiff       command to allow external programs to compare revisions
   
   (use 'hg help extensions' for information on enabling extensions)
   [10]
 
   $ echo "[extensions]" >> ../source/.hg/hgrc
   $ echo "extdiff=" >> ../source/.hg/hgrc
 
   $ hg debugextensions -R ../source
   extdiff
   share
   $ hg extdiff -R ../source -p echo
 
 BROKEN: the command below will not work if config of shared source is not loaded
 on dispatch but debugextensions says that extension
 is loaded
   $ hg debugextensions
   extdiff
   share
 
   $ hg extdiff -p echo
 
 However, local .hg/hgrc should override the config set by share source
 
   $ echo "[ui]" >> .hg/hgrc
   $ echo "curses=false" >> .hg/hgrc
 
   $ hg showconfig ui.curses
   false
 
   $ HGEDITOR=cat hg config --shared
   [ui]
   curses=true
   [extensions]
   extdiff=
 
   $ HGEDITOR=cat hg config --local
   [ui]
   curses=false
 
 Testing that hooks set in source repository also runs in shared repo
 
   $ cd ../source
   $ cat <<EOF >> .hg/hgrc
   > [extensions]
   > hooklib=
   > [hooks]
   > pretxnchangegroup.reject_merge_commits = \
   >   python:hgext.hooklib.reject_merge_commits.hook
   > EOF
 
   $ cd ..
   $ hg clone source cloned
   updating to branch default
   3 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd cloned
   $ hg up 0
   0 files updated, 0 files merged, 2 files removed, 0 files unresolved
   $ echo bar > bar
   $ hg ci -Aqm "added bar"
   $ hg merge
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   (branch merge, don't forget to commit)
   $ hg ci -m "merge commit"
 
   $ hg push ../source
   pushing to ../source
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   error: pretxnchangegroup.reject_merge_commits hook failed: bcde3522682d rejected as merge on the same branch. Please consider rebase.
   transaction abort!
   rollback completed
   abort: bcde3522682d rejected as merge on the same branch. Please consider rebase.
   [255]
 
   $ hg push ../shared1
   pushing to ../shared1
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   error: pretxnchangegroup.reject_merge_commits hook failed: bcde3522682d rejected as merge on the same branch. Please consider rebase.
   transaction abort!
   rollback completed
   abort: bcde3522682d rejected as merge on the same branch. Please consider rebase.
   [255]
 
 Test that if share source config is untrusted, we dont read it
 
   $ cd ../shared1
 
   $ cat << EOF > $TESTTMP/untrusted.py
   > from mercurial import scmutil, util
   > def uisetup(ui):
   >     class untrustedui(ui.__class__):
   >         def _trusted(self, fp, f):
   >             if util.normpath(fp.name).endswith(b'source/.hg/hgrc'):
   >                 return False
   >             return super(untrustedui, self)._trusted(fp, f)
   >     ui.__class__ = untrustedui
   > EOF
 
   $ hg showconfig hooks
   hooks.pretxnchangegroup.reject_merge_commits=python:hgext.hooklib.reject_merge_commits.hook
 
   $ hg showconfig hooks --config extensions.untrusted=$TESTTMP/untrusted.py
   [1]
 
 Update the source repository format and check that shared repo works
 
   $ cd ../source
 
 Disable zstd related tests because its not present on pure version
 #if zstd
   $ echo "[format]" >> .hg/hgrc
   $ echo "revlog-compression=zstd" >> .hg/hgrc
 
   $ hg debugupgraderepo --run -q
   upgrade will perform the following actions:
   
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, share-safe, sparserevlog, store (no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, share-safe, sparserevlog, store (dirstate-v2 !)
      added: revlog-compression-zstd
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   $ hg log -r .
   changeset:   1:5f6d8a4bf34a
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     added b
   
 #endif
   $ echo "[format]" >> .hg/hgrc
   $ echo "use-persistent-nodemap=True" >> .hg/hgrc
 
   $ hg debugupgraderepo --run -q -R ../shared1
   abort: cannot upgrade repository; unsupported source requirement: shared
   [255]
 
   $ hg debugupgraderepo --run -q
   upgrade will perform the following actions:
   
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, share-safe, sparserevlog, store (no-zstd no-dirstate-v2 !)
      preserved: dotencode, fncache, generaldelta, revlog-compression-zstd, revlogv1, share-safe, sparserevlog, store (zstd no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, share-safe, sparserevlog, store (no-zstd dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlog-compression-zstd, revlogv1, share-safe, sparserevlog, store (zstd dirstate-v2 !)
      added: persistent-nodemap
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   $ hg log -r .
   changeset:   1:5f6d8a4bf34a
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     added b
   
 
 Shared one should work
   $ cd ../shared1
   $ hg log -r .
   changeset:   2:155349b645be
   tag:         tip
   user:        test
   date:        Thu Jan 01 00:00:00 1970 +0000
   summary:     added c
   
 
 Testing that nonsharedrc is loaded for source and not shared
 
   $ cd ../source
   $ touch .hg/hgrc-not-shared
   $ echo "[ui]" >> .hg/hgrc-not-shared
   $ echo "traceback=true" >> .hg/hgrc-not-shared
 
   $ hg showconfig ui.traceback
   true
 
   $ HGEDITOR=cat hg config --non-shared
   [ui]
   traceback=true
 
   $ cd ../shared1
   $ hg showconfig ui.traceback
   [1]
 
 Unsharing works
 
   $ hg unshare
 
 Test that source config is added to the shared one after unshare, and the config
 of current repo is still respected over the config which came from source config
   $ cd ../cloned
   $ hg push ../shared1
   pushing to ../shared1
   searching for changes
   adding changesets
   adding manifests
   adding file changes
   error: pretxnchangegroup.reject_merge_commits hook failed: bcde3522682d rejected as merge on the same branch. Please consider rebase.
   transaction abort!
   rollback completed
   abort: bcde3522682d rejected as merge on the same branch. Please consider rebase.
   [255]
   $ hg showconfig ui.curses -R ../shared1
   false
 
   $ cd ../
 
 Test that upgrading using debugupgraderepo works
 =================================================
 
   $ hg init non-share-safe --config format.use-share-safe=false
   $ cd non-share-safe
   $ hg debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   sparserevlog
   store
   $ echo foo > foo
   $ hg ci -Aqm 'added foo'
   $ echo bar > bar
   $ hg ci -Aqm 'added bar'
 
 Create a share before upgrading
 
   $ cd ..
   $ hg share non-share-safe nss-share
   updating working directory
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ hg debugrequirements -R nss-share
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   shared
   sparserevlog
   store
   $ cd non-share-safe
 
 Upgrade
 
   $ hg debugupgraderepo -q
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store (no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, sparserevlog, store (dirstate-v2 !)
      added: share-safe
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   $ hg debugupgraderepo --run
   upgrade will perform the following actions:
   
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store (no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, sparserevlog, store (dirstate-v2 !)
      added: share-safe
   
   share-safe
      Upgrades a repository to share-safe format so that future shares of this repository share its requirements and configs.
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   beginning upgrade...
   repository locked and read-only
   creating temporary repository to stage upgraded data: $TESTTMP/non-share-safe/.hg/upgrade.* (glob)
   (it is safe to interrupt this process any time before data migration completes)
   upgrading repository requirements
   removing temporary repository $TESTTMP/non-share-safe/.hg/upgrade.* (glob)
   repository upgraded to share safe mode, existing shares will still work in old non-safe mode. Re-share existing shares to use them in safe mode New shares will be created in safe mode.
 
   $ hg debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   share-safe
   sparserevlog
   store
 
   $ cat .hg/requires
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   share-safe
 
   $ cat .hg/store/requires
   dotencode
   fncache
   generaldelta
   revlogv1
   sparserevlog
   store
 
   $ hg log -GT "{node}: {desc}\n"
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
 Make sure existing shares dont work with default config
 
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share
   abort: version mismatch: source uses share-safe functionality while the current share does not
   (see `hg help config.format.use-share-safe` for more information)
   [255]
 
 
 Create a safe share from upgrade one
 
   $ cd ..
   $ hg share non-share-safe ss-share
   updating working directory
   2 files updated, 0 files merged, 0 files removed, 0 files unresolved
   $ cd ss-share
   $ hg log -GT "{node}: {desc}\n"
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
   $ cd ../non-share-safe
 
 Test that downgrading works too
 
   $ cat >> $HGRCPATH <<EOF
   > [extensions]
   > share =
   > [format]
   > use-share-safe = False
   > EOF
 
   $ hg debugupgraderepo -q
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store (no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, sparserevlog, store (dirstate-v2 !)
      removed: share-safe
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   $ hg debugupgraderepo --run
   upgrade will perform the following actions:
   
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store (no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, sparserevlog, store (dirstate-v2 !)
      removed: share-safe
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   beginning upgrade...
   repository locked and read-only
   creating temporary repository to stage upgraded data: $TESTTMP/non-share-safe/.hg/upgrade.* (glob)
   (it is safe to interrupt this process any time before data migration completes)
   upgrading repository requirements
   removing temporary repository $TESTTMP/non-share-safe/.hg/upgrade.* (glob)
   repository downgraded to not use share safe mode, existing shares will not work and needs to be reshared.
 
   $ hg debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   sparserevlog
   store
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   sparserevlog
   store
 
   $ test -f .hg/store/requires
   [1]
 
   $ hg log -GT "{node}: {desc}\n"
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
 Make sure existing shares still works
 
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
   $ hg log -GT "{node}: {desc}\n" -R ../ss-share
   abort: share source does not support share-safe requirement
   (see `hg help config.format.use-share-safe` for more information)
   [255]
 
 Testing automatic downgrade of shares when config is set
 
   $ touch ../ss-share/.hg/wlock
   $ hg log -GT "{node}: {desc}\n" -R ../ss-share --config share.safe-mismatch.source-not-safe=downgrade-abort
   abort: failed to downgrade share, got error: Lock held
   (see `hg help config.format.use-share-safe` for more information)
   [255]
   $ rm ../ss-share/.hg/wlock
 
   $ hg log -GT "{node}: {desc}\n" -R ../ss-share --config share.safe-mismatch.source-not-safe=downgrade-abort
   repository downgraded to not use share-safe mode
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
   $ hg log -GT "{node}: {desc}\n" -R ../ss-share
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
 
 Testing automatic upgrade of shares when config is set
 
   $ hg debugupgraderepo -q --run --config format.use-share-safe=True
   upgrade will perform the following actions:
   
   requirements
      preserved: dotencode, fncache, generaldelta, revlogv1, sparserevlog, store (no-dirstate-v2 !)
      preserved: dotencode, exp-rc-dirstate-v2, fncache, generaldelta, revlogv1, sparserevlog, store (dirstate-v2 !)
      added: share-safe
   
   processed revlogs:
     - all-filelogs
     - changelog
     - manifest
   
   repository upgraded to share safe mode, existing shares will still work in old non-safe mode. Re-share existing shares to use them in safe mode New shares will be created in safe mode.
   $ hg debugrequirements
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   revlogv1
   share-safe
   sparserevlog
   store
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share
   abort: version mismatch: source uses share-safe functionality while the current share does not
   (see `hg help config.format.use-share-safe` for more information)
   [255]
 
 Check that if lock is taken, upgrade fails but read operation are successful
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share --config share.safe-mismatch.source-safe=upgra
   abort: share-safe mismatch with source.
   Unrecognized value 'upgra' of `share.safe-mismatch.source-safe` set.
   (see `hg help config.format.use-share-safe` for more information)
   [255]
   $ touch ../nss-share/.hg/wlock
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share --config share.safe-mismatch.source-safe=upgrade-allow
   failed to upgrade share, got error: Lock held
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share --config share.safe-mismatch.source-safe=upgrade-allow --config share.safe-mismatch.source-safe.warn=False
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share --config share.safe-mismatch.source-safe=upgrade-abort
   abort: failed to upgrade share, got error: Lock held
   (see `hg help config.format.use-share-safe` for more information)
   [255]
 
   $ rm ../nss-share/.hg/wlock
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share --config share.safe-mismatch.source-safe=upgrade-abort
   repository upgraded to use share-safe mode
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   
 
 Test that unshare works
 
   $ hg unshare -R ../nss-share
   $ hg log -GT "{node}: {desc}\n" -R ../nss-share
   @  f63db81e6dde1d9c78814167f77fb1fb49283f4f: added bar
   |
   o  f3ba8b99bb6f897c87bbc1c07b75c6ddf43a4f77: added foo
   

tests/test-sparse-requirement.t

@@ -1,81 +1,81 b''
   $ hg init repo
   $ cd repo
 
   $ touch a.html b.html c.py d.py
 
   $ cat > frontend.sparse << EOF
   > [include]
   > *.html
   > EOF
 
   $ hg -q commit -A -m initial
 
   $ echo 1 > a.html
   $ echo 1 > c.py
   $ hg commit -m 'commit 1'
 
 Enable sparse profile
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
   $ hg debugsparse --config extensions.sparse= --enable-profile frontend.sparse
   $ ls -A
   .hg
   a.html
   b.html
 
 Requirement for sparse added when sparse is enabled
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-sparse
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 Client without sparse enabled reacts properly
 
   $ hg files
   abort: repository is using sparse feature but sparse is not enabled; enable the "sparse" extensions to access
   [255]
 
 Requirement for sparse is removed when sparse is disabled
 
   $ hg debugsparse --reset --config extensions.sparse=
 
   $ cat .hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
   testonly-simplestore (reposimplestore !)
 
 And client without sparse can access
 
   $ hg files
   a.html
   b.html
   c.py
   d.py
   frontend.sparse

tests/test-sqlitestore.t

@@ -1,131 +1,131 b''
 #require sqlite no-chg
 
 The sqlitestore backend leaves transactions around when used with chg.
 Since this backend is primarily intended as proof-of-concept for
 alternative storage backends, disable it for chg test runs to avoid
 the instability.
 
   $ cat >> $HGRCPATH <<EOF
   > [extensions]
   > sqlitestore =
   > EOF
 
 New repo should not use SQLite by default
 
   $ hg init empty-no-sqlite
   $ cat empty-no-sqlite/.hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
 storage.new-repo-backend=sqlite is recognized
 
   $ hg --config storage.new-repo-backend=sqlite init empty-sqlite
   $ cat empty-sqlite/.hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-sqlite-001
   exp-sqlite-comp-001=zstd (zstd !)
   exp-sqlite-comp-001=$BUNDLE2_COMPRESSIONS$ (no-zstd !)
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
   $ cat >> $HGRCPATH << EOF
   > [storage]
   > new-repo-backend = sqlite
   > EOF
 
 Can force compression to zlib
 
   $ hg --config storage.sqlite.compression=zlib init empty-zlib
   $ cat empty-zlib/.hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-sqlite-001
   exp-sqlite-comp-001=$BUNDLE2_COMPRESSIONS$
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
 Can force compression to none
 
   $ hg --config storage.sqlite.compression=none init empty-none
   $ cat empty-none/.hg/requires
   dotencode
-  exp-rc-dirstate-v2 (dirstate-v2 !)
+  dirstate-v2 (dirstate-v2 !)
   exp-sqlite-001
   exp-sqlite-comp-001=none
   fncache
   generaldelta
   persistent-nodemap (rust !)
   revlog-compression-zstd (zstd !)
   revlogv1
   sparserevlog
   store
 
 Can make a local commit
 
   $ hg init local-commit
   $ cd local-commit
   $ echo 0 > foo
   $ hg commit -A -m initial
   adding foo
 
 That results in a row being inserted into various tables
 
   $ sqlite3 .hg/store/db.sqlite -init /dev/null << EOF
   > SELECT * FROM filepath;
   > EOF
   1|foo
 
   $ sqlite3 .hg/store/db.sqlite -init /dev/null << EOF
   > SELECT * FROM fileindex;
   > EOF
   1|1|0|-1|-1|0|0|1||6/\xef(L\xe2\xca\x02\xae\xcc\x8d\xe6\xd5\xe8\xa1\xc3\xaf\x05V\xfe (esc)
 
   $ sqlite3 .hg/store/db.sqlite -init /dev/null << EOF
   > SELECT * FROM delta;
   > EOF
   1|1|	\xd2\xaf\x8d\xd2"\x01\xdd\x8dH\xe5\xdc\xfc\xae\xd2\x81\xff\x94"\xc7|0 (esc)
   
 
 Tracking multiple files works
 
   $ echo 1 > bar
   $ hg commit -A -m 'add bar'
   adding bar
 
   $ sqlite3 .hg/store/db.sqlite -init /dev/null << EOF
   > SELECT * FROM filedata ORDER BY id ASC;
   > EOF
   1|1|foo|0|6/\xef(L\xe2\xca\x02\xae\xcc\x8d\xe6\xd5\xe8\xa1\xc3\xaf\x05V\xfe|-1|-1|0|0|1| (esc)
   2|2|bar|0|\xb8\xe0/d3s\x80!\xa0e\xf9Au\xc7\xcd#\xdb_\x05\xbe|-1|-1|1|0|2| (esc)
 
 Multiple revisions of a file works
 
   $ echo a >> foo
   $ hg commit -m 'modify foo'
 
   $ sqlite3 .hg/store/db.sqlite -init /dev/null << EOF
   > SELECT * FROM filedata ORDER BY id ASC;
   > EOF
   1|1|foo|0|6/\xef(L\xe2\xca\x02\xae\xcc\x8d\xe6\xd5\xe8\xa1\xc3\xaf\x05V\xfe|-1|-1|0|0|1| (esc)
   2|2|bar|0|\xb8\xe0/d3s\x80!\xa0e\xf9Au\xc7\xcd#\xdb_\x05\xbe|-1|-1|1|0|2| (esc)
   3|1|foo|1|\xdd\xb3V\xcd\xde1p@\xf7\x8e\x90\xb8*\x8b,\xe9\x0e\xd6j+|0|-1|2|0|3|1 (esc)
 
   $ cd ..