Skip to content

Commit

Permalink
Fix issue progit#448: 3.2 Git Branching -- possibly wrong explanation…
Browse files Browse the repository at this point in the history
… (upstream vs. downstream)
  • Loading branch information
YueLinHo committed Mar 14, 2016
1 parent 3f34aa2 commit 3a04918
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ Fast-forward
----

You'll notice the phrase ``fast-forward'' in that merge.
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.
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.
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.''

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

0 comments on commit 3a04918

Please sign in to comment.