@@ -415,9 +415,9 @@ i.e. commits that would be excluded by gitlink:git-log[1]'s
415
415
the `rebase-cousins` mode is turned on, such commits are instead rebased
416
416
onto `<upstream>` (or `<onto>`, if specified).
417
417
+
418
- The `--rebase-merges` mode is similar in spirit to `--preserve-merges`, but
419
- in contrast to that option works well in interactive rebases: commits can be
420
- reordered, inserted and dropped at will.
418
+ The `--rebase-merges` mode is similar in spirit to the deprecated
419
+ `--preserve-merges`, but in contrast to that option works well in interactive
420
+ rebases: commits can be reordered, inserted and dropped at will.
421
421
+
422
422
It is currently only possible to recreate the merge commits using the
423
423
`recursive` merge strategy; Different merge strategies can be used only via
@@ -427,9 +427,10 @@ See also REBASING MERGES and INCOMPATIBLE OPTIONS below.
427
427
428
428
-p::
429
429
--preserve-merges::
430
- Recreate merge commits instead of flattening the history by replaying
431
- commits a merge commit introduces. Merge conflict resolutions or manual
432
- amendments to merge commits are not preserved.
430
+ [DEPRECATED: use `--rebase-merges` instead] Recreate merge commits
431
+ instead of flattening the history by replaying commits a merge commit
432
+ introduces. Merge conflict resolutions or manual amendments to merge
433
+ commits are not preserved.
433
434
+
434
435
This uses the `--interactive` machinery internally, but combining it
435
436
with the `--interactive` option explicitly is generally not a good
@@ -1020,11 +1021,11 @@ merge cmake
1020
1021
1021
1022
BUGS
1022
1023
----
1023
- The todo list presented by `--preserve-merges --interactive` does not
1024
- represent the topology of the revision graph. Editing commits and
1025
- rewording their commit messages should work fine, but attempts to
1026
- reorder commits tend to produce counterintuitive results. Use
1027
- `--rebase-merges` in such scenarios instead.
1024
+ The todo list presented by the deprecated `--preserve-merges --interactive`
1025
+ does not represent the topology of the revision graph (use `--rebase-merges`
1026
+ instead). Editing commits and rewording their commit messages should work
1027
+ fine, but attempts to reorder commits tend to produce counterintuitive results.
1028
+ Use `--rebase-merges` in such scenarios instead.
1028
1029
1029
1030
For example, an attempt to rearrange
1030
1031
------------
0 commit comments