Show More
@@ -0,0 +1,59 b'' | |||||
|
1 | '''This is the last release to support Python 2. Mercurial is Python 3 only starting with 6.2''' | |||
|
2 | ||||
|
3 | = Mercurial 6.1rc0 = | |||
|
4 | ||||
|
5 | == New Features == | |||
|
6 | * Added a way of specifying required extensions that prevent Mercurial from starting if they are not found. See `hg help config.extensions`. | |||
|
7 | * Merge conflict markers have been made clearer (see backwards compatibility below) | |||
|
8 | * Improve detailed error codes | |||
|
9 | * Added a hint about mangled whitespace on bad patch | |||
|
10 | * Explain which order the commits are presented in `chistedit` | |||
|
11 | * Introduce a `dirstate-tracked-hint` feature to help automation keep track of changes to tracked files. See `hg help config.use-dirstate-tracked-hint`. | |||
|
12 | * Shared repositories can be upgraded if the upgrade is specific to the share. For now, this only applies to `dirstate-v2` and `dirstate-tracked-hint`. | |||
|
13 | * When using the `narrow` extension, non-conflicting changes to files outside of the narrow specification can now be merged. | |||
|
14 | * When cloning a repository using stream-clone, the client can now control the repository format variants to use as long as the stream content does not restrict that variant. | |||
|
15 | ||||
|
16 | == Default Format Change == | |||
|
17 | ||||
|
18 | These changes affect newly created repositories (or new clones) done with Mercurial 6.1. | |||
|
19 | ||||
|
20 | * The `share-safe` format variant is now enabled by default. It makes configuration and requirements more consistent across repository and their shares. This introduces a behavior change as shares from a repository using the new format will also use their main repository's configuration. See `hg help config.format.use-share-safe` for details about the feature and the available options for auto-upgrading existing shares. | |||
|
21 | ||||
|
22 | ||||
|
23 | == New Experimental Features == | |||
|
24 | * The pure Rust version of Mercurial called `rhg` added support for most common invocations of `hg status`. See `hg help rust.rhg` for details on how to try it out. | |||
|
25 | * `rhg` supports narrow clones and sparse checkouts. | |||
|
26 | ||||
|
27 | == Bug Fixes == | |||
|
28 | ||||
|
29 | * '''Obsolete revisions are skipped while computing heads. In conjunction with the `evolve` extension >= 10.5.0, this leads to massive exchange (push/pull) speedups in repositories with a lot of heads and/or obsolete revisions.''' | |||
|
30 | * Stream-clones now properly advertise all requirements needed. This can result in the stream-clone feature being disabled for some clients using < 6.0.2. A small bugfix patch for these older client is available if necessary. | |||
|
31 | * The `--no-check` and `--no-merge` flags now properly overwrite the behavior from `commands.update.check` | |||
|
32 | * `rhg`'s fallback detection is more robust in general in the presence of more advanced configs | |||
|
33 | * `rhg`'s `blackbox` now supports milliseconds by default and uses the same ISO 8601 format as the Python implementation | |||
|
34 | * Fix `rhg` crash on non-generaldelta revlogs | |||
|
35 | * The `lfs`, `largefiles` and `sparse` extensions now correctly take the appropriate lock before writing requirements | |||
|
36 | * The `notify` extension does not produce errors anymore if a revision is not found | |||
|
37 | * Remove unnecessary and overly strict check for divergence in `hg fix` | |||
|
38 | * Windows compatibility improvements | |||
|
39 | * Miscellaneous Python 3 and typing improvements | |||
|
40 | * Many other small or internal fixes | |||
|
41 | ||||
|
42 | == Backwards Compatibility Changes == | |||
|
43 | ||||
|
44 | * The use of `share-safe`, means shares (of new repositories) will also use their main repository's configuration see the `Default Format Change` section for details. | |||
|
45 | * The fix to stream-clone requirements advertising means some requirements previously (wrongly) omitted are now sent. This can confuse client using a Mercurial version < 6.0.2. The client would consider these requirements unsupported even if it actually know them. If you encounter this, either upgrade your client or apply the necessary patch. | |||
|
46 | * The labels passed to merge tools have changed slightly. Merge tools can get labels passed to them if you include `$labellocal`, `$labelbase`, and/or `$labelother` in the `merge-tool.<tool name>.args` configuration. These labels used to have some space-padding, and truncation to fit within 72 columns. Both the padding and the truncation has been removed. | |||
|
47 | * Some of the text in labels passed to merge tools has changed. For example, in conflicts while running `hg histedit`, the labels used to be "local", "base", and "histedit". They are now "already edited", "parent of current change", and "current change", respectively. | |||
|
48 | * The computation of namedbranch heads now ignores obsolete revisions. User of the Changeset Evolution feature may see a change in location and numbers of heads of each named branches (and topic). | |||
|
49 | * The remotefilelog extension now requires an appropriate excludepattern for subrepositories. | |||
|
50 | * `debugsparse`'s interface has been reworked to be more flexible. Since it's a debug command it is not actually a breaking change, but it is worth noting here. | |||
|
51 | * Temporary files for merges are now all inside a `hgmerge` directory instead of at the root of `TMPDIR`. The corresponding experimental `mergetempdirprefix` config option has been removed. | |||
|
52 | ||||
|
53 | == Internal API Changes == | |||
|
54 | ||||
|
55 | * The dirstate API received minor modifications. | |||
|
56 | ||||
|
57 | == Miscellaneous == | |||
|
58 | ||||
|
59 | * Removed exchange-v2. It was a prototype that had never been in a working state and had been left untouched since 2017. |
@@ -1,48 +1,18 b'' | |||||
|
1 | = Mercurial XXX = | |||
|
2 | ||||
1 | == New Features == |
|
3 | == New Features == | |
2 |
|
4 | |||
3 |
|
||||
4 | == Default Format Change == |
|
5 | == Default Format Change == | |
5 |
|
6 | |||
6 |
These changes affect |
|
7 | These changes affect newly created repositories (or new clones) done with | |
7 |
Mercurial |
|
8 | Mercurial XXX. | |
8 |
|
||||
9 | The `share-safe` format variant is now enabled by default. It makes |
|
|||
10 | configuration and requirements more consistent across repository and their |
|
|||
11 | shares. This introduces a behavior change as shares from a repository using the |
|
|||
12 | new format will also use their main repository's configuration. |
|
|||
13 |
|
||||
14 | See `hg help config.format.use-share-safe` for details about the feature and |
|
|||
15 | the available options for auto-upgrading existing shares. |
|
|||
16 |
|
||||
17 |
|
9 | |||
18 | == New Experimental Features == |
|
10 | == New Experimental Features == | |
19 |
|
11 | |||
20 | == Bug Fixes == |
|
12 | == Bug Fixes == | |
21 |
|
13 | |||
22 | The `--no-check` and `--no-merge` now properly overwrite the behavior from `commands.update.check`. |
|
|||
23 |
|
||||
24 | == Backwards Compatibility Changes == |
|
14 | == Backwards Compatibility Changes == | |
25 |
|
15 | |||
26 | The remotefilelog extension now requires an appropiate excludepattern |
|
|||
27 | for subrepositories. |
|
|||
28 |
|
||||
29 | The labels passed to merge tools have changed slightly. Merge tools can get |
|
|||
30 | labels passed to them if you include `$labellocal`, `$labelbase`, and/or |
|
|||
31 | `$labelother` in the `merge-tool.<tool name>.args` configuration. These labels |
|
|||
32 | used to have some space-padding, and truncation to fit within 72 columns. Both |
|
|||
33 | the padding and the truncation has been removed. |
|
|||
34 |
|
||||
35 | Some of the text in labels passed to merge tools has changed. For example, |
|
|||
36 | in conflicts while running `hg histedit`, the labels used to be "local", |
|
|||
37 | "base", and "histedit". They are now "already edited", |
|
|||
38 | "parent of current change", and "current change", respectively. |
|
|||
39 |
|
||||
40 | The use of `share-safe`, means shares (of new repositories) will also use their |
|
|||
41 | main repository's configuration see the `Default Format Change` section |
|
|||
42 | for details. |
|
|||
43 |
|
||||
44 | == Internal API Changes == |
|
16 | == Internal API Changes == | |
45 |
|
17 | |||
46 | The following functions have been removed: |
|
18 | == Miscellaneous == | |
47 |
|
||||
48 | Miscellaneous: |
|
General Comments 0
You need to be logged in to leave comments.
Login now