to track upstream remotes/origin/v1 branch and checks out ``v1`` into
the working directory.
-Some commands, like ``git status``, report the difference between
-local and remote branches. Please remember they only do comparison
-with remote-tracking branches in your local repository, and the state
-of those remote-tracking branches can be outdated. To update
-remote-tracking branches you either fetch and merge (or rebase)
-commits from the remote repository or update remote-tracking branches
-without updating local branches.
+Some commands, like ``git status --branch`` and ``git branch --verbose``,
+report the difference between local and remote branches.
+Please remember they only do comparison with remote-tracking branches
+in your local repository, and the state of those remote-tracking
+branches can be outdated. To update remote-tracking branches you
+either fetch and merge (or rebase) commits from the remote repository
+or update remote-tracking branches without updating local branches.
Updating local and remote-tracking branches
-------------------------------------------
+To update remote-tracking branches without updating local branches run
+``git remote update [$REMOTE...]``. For example::
+
+ $ git remote update
+ $ git remote update origin
+
+
+Fetch and pull
+''''''''''''''
+
There is a major difference between
::
for caveats; in 2.4 the push-to-deploy feature was `further improved
<https://github.com/blog/1994-git-2-4-atomic-pushes-push-to-deploy-and-more#push-to-deploy-improvements>`_.
-To update remote-tracking branches without updating local branches run
-``git remote update [$REMOTE...]``. For example::
-
- $ git remote update
- $ git remote update origin
-
Tags
''''