Mercurial > hg
view relnotes/next @ 47787:48da5c325750 stable
rewriteutil: fix crash when a rewritten message references f{6,64}
Without this, the rewriteutil logic thinks it's found a reference to the wdir
pseudo-revision, and then tries to look it up and rewrite it. Stop it from
doing that.
Amusingly, I had trouble working with this changeset when I didn't
describe the defect above using a regular expression, because it would
trigger the bug in my installed version of hg.
Differential Revision: https://phab.mercurial-scm.org/D11232
author | Augie Fackler <augie@google.com> |
---|---|
date | Thu, 29 Jul 2021 16:23:45 -0400 |
parents | ec77f709495c |
children | bad66df931b5 |
line wrap: on
line source
== New Features == * `hg config` now has a `--source` option to show where each configuration value comes from. == Default Format Change == These changes affects newly created repositories (or new clone) done with Mercurial 5.8. == New Experimental Features == == Bug Fixes == == Backwards Compatibility Changes == == Internal API Changes == The Dirstate API have been updated as the previous function leaked some internal details and did not distinct between two important cases: "We are changing parent and need to adjust the dirstate" and "some command is changing which file is tracked". To clarify the situation: * the following functions have been deprecated, - dirstate.add, - dirstate.normal, - dirstate.normallookup, - dirstate.merge, - dirstate.otherparent, - dirstate.remove, - dirstate.drop, * these new functions are added for the "adjusting parents" use-case: - dirstate.update_file, - dirstate.update_file_p1, * these new function are added for the "adjusting wc file" use-case": - dirstate.set_tracked, - dirstate.set_untracked, - dirstate.set_clean, - dirstate.set_possibly_dirty, See inline documentation of the new functions for details.