Show More
| @@ -1,67 +1,68 b'' | |||
|
|
1 | 1 | == New Features == |
|
|
2 | 2 | |
|
|
3 | 3 | * `hg purge` is now a core command using `--confirm` by default. |
|
|
4 | 4 | |
|
|
5 | 5 | * The `rev-branch-cache` is now updated incrementally whenever changesets |
|
|
6 | 6 | are added. |
|
|
7 | 7 | |
|
|
8 | 8 | * The new options `experimental.bundlecompthreads` and |
|
|
9 | 9 | `experimental.bundlecompthreads.<engine>` can be used to instruct |
|
|
10 | 10 | the compression engines for bundle operations to use multiple threads |
|
|
11 | 11 | for compression. The default is single threaded operation. Currently |
|
|
12 | 12 | only supported for zstd. |
|
|
13 | 13 | |
|
|
14 | 14 | == Default Format Change == |
|
|
15 | 15 | |
|
|
16 | 16 | These changes affects newly created repositories (or new clone) done with |
|
|
17 | 17 | Mercurial 5.8. |
|
|
18 | 18 | |
|
|
19 | 19 | * The `ZSTD` compression will now be used by default for new repositories |
|
|
20 | 20 | when available. This compression format was introduced in Mercurial 5.0, |
|
|
21 | 21 | released in May 2019. See `hg help config.format.revlog-compression` for |
|
|
22 | 22 | details. |
|
|
23 | 23 | |
|
|
24 | 24 | * Mercurial installation built with the Rust parts will now use the |
|
|
25 | 25 | "persistent nodemap" feature by default. This feature was introduced in |
|
|
26 | 26 | Mercurial 5.4 (May 2020). However Mercurial instalation built without the |
|
|
27 | 27 | fast Rust implementation will refuse to interract with them by default. |
|
|
28 | 28 | This restriction can be lifted through configuration. |
|
|
29 | 29 | |
|
|
30 | 30 | See `hg help config.format.use-persistent-nodemap` for details |
|
|
31 | 31 | |
|
|
32 | 32 | == New Experimental Features == |
|
|
33 | 33 | |
|
|
34 | 34 | * There's a new `diff.merge` config option to show the changes |
|
|
35 | 35 | relative to an automerge for merge changesets. This makes it |
|
|
36 | 36 | easier to detect and review manual changes performed in merge |
|
|
37 | 37 | changesets. It is supported by `hg diff --change`, `hg log -p` |
|
|
38 | 38 | `hg incoming -p`, and `hg outgoing -p` so far. |
|
|
39 | 39 | |
|
|
40 | 40 | |
|
|
41 | 41 | == Bug Fixes == |
|
|
42 | 42 | |
|
|
43 | * gracefully recover from inconsistent persistent-nodemap data from disk. | |
|
|
43 | 44 | |
|
|
44 | 45 | |
|
|
45 | 46 | == Backwards Compatibility Changes == |
|
|
46 | 47 | |
|
|
47 | 48 | * In normal repositories, the first parent of a changeset is not null, |
|
|
48 | 49 | unless both parents are null (like the first changeset). Some legacy |
|
|
49 | 50 | repositories violate this condition. The revlog code will now |
|
|
50 | 51 | silentely swap the parents if this condition is tested. This can |
|
|
51 | 52 | change the output of `hg log` when explicitly asking for first or |
|
|
52 | 53 | second parent. The changesets "nodeid" are not affected. |
|
|
53 | 54 | |
|
|
54 | 55 | |
|
|
55 | 56 | == Internal API Changes == |
|
|
56 | 57 | |
|
|
57 | 58 | * `changelog.branchinfo` is deprecated and will be removed after 5.8. |
|
|
58 | 59 | It is superseded by `changelogrevision.branchinfo`. |
|
|
59 | 60 | |
|
|
60 | 61 | * Callbacks for revlog.addgroup and the changelog._nodeduplicatecallback hook |
|
|
61 | 62 | now get a revision number as argument instead of a node. |
|
|
62 | 63 | |
|
|
63 | 64 | * revlog.addrevision returns the revision number instead of the node. |
|
|
64 | 65 | |
|
|
65 | 66 | * `nodes.nullid` and related constants are being phased out as part of |
|
|
66 | 67 | the deprecation of SHA1. Repository instances and related classes |
|
|
67 | 68 | provide access via `nodeconstants` and in some cases `nullid` attributes. |
General Comments 0
You need to be logged in to leave comments.
Login now