Skip to content

Commit 11fe3f7

Browse files
Martin von Zweigbergkgitster
authored andcommitted
Documentation/git-pull: clarify configuration
The sentence about 'branch.<name>.rebase' refers to the first sentence in the paragraph and not to the sentence about avoiding rebasing non-local changes. Clarify this. Signed-off-by: Martin von Zweigbergk <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 6a6c54b commit 11fe3f7

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

Documentation/git-pull.txt

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -92,12 +92,14 @@ include::merge-options.txt[]
9292
:git-pull: 1
9393

9494
--rebase::
95-
Instead of a merge, perform a rebase after fetching. If
96-
there is a remote ref for the upstream branch, and this branch
97-
was rebased since last fetched, the rebase uses that information
98-
to avoid rebasing non-local changes. To make this the default
99-
for branch `<name>`, set configuration `branch.<name>.rebase`
100-
to `true`.
95+
Rebase the current branch on top of the upstream branch after
96+
fetching. If there is a remote-tracking branch corresponding to
97+
the upstream branch and the upstream branch was rebased since last
98+
fetched, the rebase uses that information to avoid rebasing
99+
non-local changes.
100+
+
101+
See `branch.<name>.rebase` in linkgit:git-config[1] if you want to make
102+
`git pull` always use `{litdd}rebase` instead of merging.
101103
+
102104
[NOTE]
103105
This is a potentially _dangerous_ mode of operation.

0 commit comments

Comments
 (0)