Skip to content

Commit a440884

Browse files
phil-blaingitster
authored andcommitted
pull doc: correct outdated description of an example
Since f269048 (fetch: opportunistically update tracking refs, 2013-05-11), the underlying `git fetch` in `git pull <remote> <branch>` updates the configured remote-tracking branch for <branch>. However, an example in the 'Examples' section of the `git pull` documentation still states that this is not the case. Correct the description of this example. Signed-off-by: Philippe Blain <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent f6a65de commit a440884

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/git-pull.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -229,9 +229,9 @@ branch.<name>.merge options; see linkgit:git-config[1] for details.
229229
$ git pull origin next
230230
------------------------------------------------
231231
+
232-
This leaves a copy of `next` temporarily in FETCH_HEAD, but
233-
does not update any remote-tracking branches. Using remote-tracking
234-
branches, the same can be done by invoking fetch and merge:
232+
This leaves a copy of `next` temporarily in FETCH_HEAD, and
233+
updates the remote-tracking branch `origin/next`.
234+
The same can be done by invoking fetch and merge:
235235
+
236236
------------------------------------------------
237237
$ git fetch origin

0 commit comments

Comments
 (0)