Skip to content

Commit aba5cf5

Browse files
committed
Merge pull request #564 from YueLinHo/i448
Fix issue #448: 3.2 Git Branching -- possibly wrong explanation (upstream vs. downstream)
2 parents 8267a20 + 3a04918 commit aba5cf5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

book/03-git-branching/sections/basic-branching-and-merging.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Fast-forward
105105
----
106106

107107
You'll notice the phrase ``fast-forward'' in that merge.
108-
Because the commit pointed to by the branch you merged in was directly upstream of the commit you're on, Git simply moves the pointer forward.
108+
Because the commit `C4` pointed to by the branch `hotfix` you merged in was directly ahead of the commit `C2` you're on, Git simply moves the pointer forward.
109109
To phrase that another way, when you try to merge one commit with a commit that can be reached by following the first commit's history, Git simplifies things by moving the pointer forward because there is no divergent work to merge together – this is called a ``fast-forward.''
110110

111111
Your change is now in the snapshot of the commit pointed to by the `master` branch, and you can deploy the fix.

0 commit comments

Comments
 (0)