mirror of
https://github.com/git/git.git
synced 2024-10-29 21:37:53 +01:00
doc: improve readability of --rebase-merges in git-rebase
When --preserve-merges was deprecated in 427c3bd28a
a sentence
was introduced describing the difference between --rebase-merges and
--preserve-merges which is a little unclear and difficult to parse.
This patch improves readability while retaining original meaning.
Signed-off-by: Naveen Nathan <naveen@lastninja.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
d9f6f3b619
commit
d3a8caebf3
1 changed files with 2 additions and 2 deletions
|
@ -443,8 +443,8 @@ the `rebase-cousins` mode is turned on, such commits are instead rebased
|
|||
onto `<upstream>` (or `<onto>`, if specified).
|
||||
+
|
||||
The `--rebase-merges` mode is similar in spirit to the deprecated
|
||||
`--preserve-merges`, but in contrast to that option works well in interactive
|
||||
rebases: commits can be reordered, inserted and dropped at will.
|
||||
`--preserve-merges` but works with interactive rebases,
|
||||
where commits can be reordered, inserted and dropped at will.
|
||||
+
|
||||
It is currently only possible to recreate the merge commits using the
|
||||
`recursive` merge strategy; Different merge strategies can be used only via
|
||||
|
|
Loading…
Reference in a new issue