Skip to content

Commit 9af562d

Browse files
committed
Merge pull request #519 from uasi/patch-1
Fix explanation of upstream branch
2 parents 9e7cf1e + 0922ba0 commit 9af562d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

book/03-git-branching/sections/remote-branches.asc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ This gives you a local branch that you can work on that starts where `origin/ser
130130
==== Tracking Branches
131131

132132
(((branches, tracking)))(((branches, upstream)))
133-
Checking out a local branch from a remote-tracking branch automatically creates what is called a ``tracking branch'' (or sometimes an ``upstream branch'').
133+
Checking out a local branch from a remote-tracking branch automatically creates what is called a ``tracking branch'' (and the branch it tracks is called an ``upstream branch'').
134134
Tracking branches are local branches that have a direct relationship to a remote branch.
135135
If you're on a tracking branch and type `git pull`, Git automatically knows which server to fetch from and branch to merge into.
136136

@@ -177,7 +177,7 @@ Branch serverfix set up to track remote branch serverfix from origin.
177177
[NOTE]
178178
.Upstream shorthand
179179
====
180-
When you have a tracking branch set up, you can reference it with the `@{upstream}` or `@{u}` shorthand.
180+
When you have a tracking branch set up, you can reference its upstream branch with the `@{upstream}` or `@{u}` shorthand.
181181
So if you're on the `master` branch and it's tracking `origin/master`, you can say something like `git merge @{u}` instead of `git merge origin/master` if you wish.(((+++@{u}+++)))(((+++@{upstream}+++)))
182182
====
183183

0 commit comments

Comments
 (0)