Skip to content

Commit

Permalink
Merge branch 'ss/pull-rebase-preserve' into maint
Browse files Browse the repository at this point in the history
* ss/pull-rebase-preserve:
  docs: clarify what git-rebase's "-p" / "--preserve-merges" does
  docs: clarify "preserve" option wording for git-pull
  • Loading branch information
Junio C Hamano committed Mar 31, 2015
2 parents ab0fb57 + d50d31e commit ad00aeb
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 4 deletions.
5 changes: 2 additions & 3 deletions Documentation/git-pull.txt
Original file line number Diff line number Diff line change
Expand Up @@ -111,9 +111,8 @@ include::merge-options.txt[]
was rebased since last fetched, the rebase uses that information
to avoid rebasing non-local changes.
+
When preserve, also rebase the current branch on top of the upstream
branch, but pass `--preserve-merges` along to `git rebase` so that
locally created merge commits will not be flattened.
When set to preserve, rebase with the `--preserve-merges` option passed
to `git rebase` so that locally created merge commits will not be flattened.
+
When false, merge the current branch into the upstream branch.
+
Expand Down
4 changes: 3 additions & 1 deletion Documentation/git-rebase.txt
Original file line number Diff line number Diff line change
Expand Up @@ -362,7 +362,9 @@ default is `--no-fork-point`, otherwise the default is `--fork-point`.

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

0 comments on commit ad00aeb

Please sign in to comment.