diff options
author | Elijah Newren <newren@gmail.com> | 2021-08-04 23:50:53 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2021-08-05 08:57:40 -0700 |
commit | 67feccd3ba4566392774b8ed9492d7169031d4bb (patch) | |
tree | 1718ead5cb129e0db5096bf6152342c700b5686a | |
parent | git-rebase.txt: correct out-of-date and misleading text about renames (diff) | |
download | tgif-67feccd3ba4566392774b8ed9492d7169031d4bb.tar.xz |
merge-strategies.txt: add coverage of the `ort` merge strategy
Acked-by: Derrick Stolee <dstolee@microsoft.com>
Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r-- | Documentation/merge-strategies.txt | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt index b54bcf68f2..210f0f850b 100644 --- a/Documentation/merge-strategies.txt +++ b/Documentation/merge-strategies.txt @@ -95,6 +95,20 @@ subtree[=<path>];; is prefixed (or stripped from the beginning) to make the shape of two trees to match. +ort:: + This is meant as a drop-in replacement for the `recursive` + algorithm (as reflected in its acronym -- "Ostensibly + Recursive's Twin"), and will likely replace it in the future. + It fixes corner cases that the `recursive` strategy handles + suboptimally, and is significantly faster in large + repositories -- especially when many renames are involved. ++ +The `ort` strategy takes all the same options as `recursive`. +However, it ignores three of those options: `no-renames`, +`patience` and `diff-algorithm`. It always runs with rename +detection (it handles it much faster than `recursive` does), and +it specifically uses `diff-algorithm=histogram`. + resolve:: This can only resolve two heads (i.e. the current branch and another branch you pulled from) using a 3-way merge |