Skip to content

Commit 76dc2c1

Browse files
committed
doc: git-pull: delete the example
From user feedback: this example is confusing because it implies that `git pull` will run `git merge` by default, but the default is `--ff-only`. We could instead show an example of a fast-forward merge, but that may not add a lot since fast-forward merges are relatively simple. This lets us keep the description short. Signed-off-by: Julia Evans <[email protected]>
1 parent ffbb9d7 commit 76dc2c1

File tree

1 file changed

+0
-26
lines changed

1 file changed

+0
-26
lines changed

Documentation/git-pull.adoc

Lines changed: 0 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -30,32 +30,6 @@ branch. There are 4 main options for integrating the remote branch:
3030
You can also set the configuration options `pull.rebase`, `pull.squash`,
3131
or `pull.ff` with your preferred behaviour.
3232

33-
Assume the following history exists and the current branch is
34-
"`master`":
35-
36-
------------
37-
A---B---C master on origin
38-
/
39-
D---E---F---G master
40-
^
41-
origin/master in your repository
42-
------------
43-
44-
Then "`git pull`" will fetch and replay the changes from the remote
45-
`master` branch since it diverged from the local `master` (i.e., `E`)
46-
until its current commit (`C`) on top of `master` and record the
47-
result in a new commit along with the names of the two parent commits
48-
and a log message from the user describing the changes.
49-
50-
------------
51-
A---B---C origin/master
52-
/ \
53-
D---E---F---G---H master
54-
------------
55-
56-
See linkgit:git-merge[1] for details, including how conflicts
57-
are presented and handled.
58-
5933
In Git 1.7.0 or later, to cancel a conflicting merge, use
6034
`git reset --merge`. *Warning*: In older versions of Git, running 'git pull'
6135
with uncommitted changes is discouraged: while possible, it leaves you

0 commit comments

Comments
 (0)