Skip to content

Commit ad00aeb

Browse files
committed
Merge branch 'ss/pull-rebase-preserve' into maint
* ss/pull-rebase-preserve: docs: clarify what git-rebase's "-p" / "--preserve-merges" does docs: clarify "preserve" option wording for git-pull
2 parents ab0fb57 + d50d31e commit ad00aeb

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

Documentation/git-pull.txt

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -111,9 +111,8 @@ include::merge-options.txt[]
111111
was rebased since last fetched, the rebase uses that information
112112
to avoid rebasing non-local changes.
113113
+
114-
When preserve, also rebase the current branch on top of the upstream
115-
branch, but pass `--preserve-merges` along to `git rebase` so that
116-
locally created merge commits will not be flattened.
114+
When set to preserve, rebase with the `--preserve-merges` option passed
115+
to `git rebase` so that locally created merge commits will not be flattened.
117116
+
118117
When false, merge the current branch into the upstream branch.
119118
+

Documentation/git-rebase.txt

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -362,7 +362,9 @@ default is `--no-fork-point`, otherwise the default is `--fork-point`.
362362

363363
-p::
364364
--preserve-merges::
365-
Instead of ignoring merges, try to recreate them.
365+
Recreate merge commits instead of flattening the history by replaying
366+
commits a merge commit introduces. Merge conflict resolutions or manual
367+
amendments to merge commits are not preserved.
366368
+
367369
This uses the `--interactive` machinery internally, but combining it
368370
with the `--interactive` option explicitly is generally not a good

0 commit comments

Comments
 (0)