Skip to content

Commit 129260c

Browse files
sschuberthgitster
authored andcommitted
docs: clarify "preserve" option wording for git-pull
The "also" sounds as if "preserve" does a rebase as an additional step that "true" would not do, but that is not the case. Clarify this by omitting "also", and rewording the sentence a bit. Signed-off-by: Sebastian Schuberth <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 282616c commit 129260c

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
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
+

0 commit comments

Comments
 (0)