2041 ----------- |
2041 ----------- |
2042 |
2042 |
2043 Control the strategy Mercurial uses internally to store history. Options in this |
2043 Control the strategy Mercurial uses internally to store history. Options in this |
2044 category impact performance and repository size. |
2044 category impact performance and repository size. |
2045 |
2045 |
|
2046 ``revlog.issue6528.fix-incoming`` |
|
2047 Version 5.8 of Mercurial had a bug leading to altering the parent of file |
|
2048 revision with copy information (or any other metadata) on exchange. This |
|
2049 leads to the copy metadata to be overlooked by various internal logic. The |
|
2050 issue was fixed in Mercurial 5.8.1. |
|
2051 (See https://bz.mercurial-scm.org/show_bug.cgi?id=6528 for details) |
|
2052 |
|
2053 As a result Mercurial is now checking and fixing incoming file revisions to |
|
2054 make sure there parents are in the right order. This behavior can be |
|
2055 disabled by setting this option to `no`. This apply to revisions added |
|
2056 through push, pull, clone and unbundle. |
|
2057 |
|
2058 To fix affected revisions that already exist within the repository, one can |
|
2059 use :hg:`debug-repair-issue-6528`. |
|
2060 |
2046 ``revlog.optimize-delta-parent-choice`` |
2061 ``revlog.optimize-delta-parent-choice`` |
2047 When storing a merge revision, both parents will be equally considered as |
2062 When storing a merge revision, both parents will be equally considered as |
2048 a possible delta base. This results in better delta selection and improved |
2063 a possible delta base. This results in better delta selection and improved |
2049 revlog compression. This option is enabled by default. |
2064 revlog compression. This option is enabled by default. |
2050 |
2065 |