Skip to content

Commit 7948b49

Browse files
dschogitster
authored andcommitted
rebase docs: recommend -r over -p
The `--preserve-merges` option is now deprecated in favor of `--rebase-merges`; Let's stop recommending the former. Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 7401ab9 commit 7948b49

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

Documentation/git-rebase.txt

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -670,7 +670,8 @@ $ git rebase -i HEAD~5
670670

671671
And move the first patch to the end of the list.
672672

673-
You might want to preserve merges, if you have a history like this:
673+
You might want to recreate merge commits, e.g. if you have a history
674+
like this:
674675

675676
------------------
676677
X
@@ -684,7 +685,7 @@ Suppose you want to rebase the side branch starting at "A" to "Q". Make
684685
sure that the current HEAD is "B", and call
685686

686687
-----------------------------
687-
$ git rebase -i -p --onto Q O
688+
$ git rebase -i -r --onto Q O
688689
-----------------------------
689690

690691
Reordering and editing commits usually creates untested intermediate

0 commit comments

Comments
 (0)