From fd1ba429233aeabf7e98ea93c526c0f83f79b04b Mon Sep 17 00:00:00 2001 From: Oleg Broytman Date: Wed, 15 Jun 2016 20:42:26 +0300 Subject: [PATCH] ``git status --branch`` and ``git branch --verbose`` --- pep-103.txt | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pep-103.txt b/pep-103.txt index f17f08f..bf8e389 100644 --- a/pep-103.txt +++ b/pep-103.txt @@ -193,13 +193,13 @@ remote-tracking branches, creates a local branch ``v1``, configure it 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 -- 2.39.2