You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/03-git-branching/sections/remote-branches.asc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ This gives you a local branch that you can work on that starts where `origin/ser
130
130
==== Tracking Branches
131
131
132
132
(((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'').
134
134
Tracking branches are local branches that have a direct relationship to a remote branch.
135
135
If you're on a tracking branch and type `git pull`, Git automatically knows which server to fetch from and branch to merge into.
136
136
@@ -177,7 +177,7 @@ Branch serverfix set up to track remote branch serverfix from origin.
177
177
[NOTE]
178
178
.Upstream shorthand
179
179
====
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.
181
181
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}+++)))
0 commit comments