@@ -87,44 +87,33 @@ no-renames;;
8787 configuration variable.
8888 See also linkgit:git-diff[1] `--no-renames` .
8989
90- subtree[=<path >];;
91- This option is a more advanced form of 'subtree' strategy, where
92- the strategy makes a guess on how two trees must be shifted to
93- match with each other when merging. Instead, the specified path
94- is prefixed (or stripped from the beginning) to make the shape of
95- two trees to match.
96-
97- recursive::
98- This can only resolve two heads using a 3-way merge
99- algorithm. When there is more than one common
100- ancestor that can be used for 3-way merge, it creates a
101- merged tree of the common ancestors and uses that as
102- the reference tree for the 3-way merge. This has been
103- reported to result in fewer merge conflicts without
104- causing mismerges by tests done on actual merge commits
105- taken from Linux 2.6 kernel development history.
106- Additionally this can detect and handle merges involving
107- renames. It does not make use of detected copies. This was
108- the default strategy for resolving two heads from Git v0.99.9k
109- until v2.33.0.
110- +
111- For a path that is a submodule, the same caution as 'ort' applies to this
112- strategy.
113- +
114- The 'recursive' strategy takes the same options as 'ort' . However,
115- there are two additional options that 'ort' ignores (not documented
116- above) that are potentially useful with the 'recursive' strategy:
90+ histogram;;
91+ Deprecated synonym for `diff-algorithm=histogram` .
11792
11893patience;;
11994 Deprecated synonym for `diff-algorithm=patience` .
12095
121- diff-algorithm=[patience |minimal|histogram| myers];;
96+ diff-algorithm=[histogram |minimal|myers|patience ];;
12297 Use a different diff algorithm while merging, which can help
12398 avoid mismerges that occur due to unimportant matching lines
12499 (such as braces from distinct functions). See also
125100 linkgit:git-diff[1] `--diff-algorithm` . Note that `ort`
126- specifically uses `diff-algorithm=histogram` , while `recursive`
127- defaults to the `diff.algorithm` config setting.
101+ defaults to `diff-algorithm=histogram` , while regular diffs
102+ currently default to the `diff.algorithm` config setting.
103+
104+ subtree[=<path >];;
105+ This option is a more advanced form of 'subtree' strategy, where
106+ the strategy makes a guess on how two trees must be shifted to
107+ match with each other when merging. Instead, the specified path
108+ is prefixed (or stripped from the beginning) to make the shape of
109+ two trees to match.
110+
111+ recursive::
112+ This is now a synonym for `ort` . It was an alternative
113+ implementation until v2.49.0, but was redirected to mean `ort`
114+ in v2.50.0. The previous recursive strategy was the default
115+ strategy for resolving two heads from Git v0.99.9k until
116+ v2.33.0.
128117
129118resolve::
130119 This can only resolve two heads (i.e. the current branch
@@ -145,7 +134,7 @@ ours::
145134 ignoring all changes from all other branches. It is meant to
146135 be used to supersede old development history of side
147136 branches. Note that this is different from the -Xours option to
148- the 'recursive ' merge strategy.
137+ the 'ort ' merge strategy.
149138
150139subtree::
151140 This is a modified `ort` strategy. When merging trees A and
0 commit comments