[PATCH] Documentation/git-push.txt: fix typo in remote tracking branch path
- From
- Brandon Casey <bcasey@nvidia.com>
- Date
- Nov 27, 2012, 00:55 UTC
- Message-ID
- <1353977748-17110-1-git-send-email-bcasey@nvidia.com>
From: Brandon Casey <drafnel@gmail.com>
This example in the documentation seems to be trying to describe the likely remote tracking branch that will be updated by a push to the "origin" remote with the destination branch 'satellite/master', but it forgot to specify the remote name in the path specification.
So,
refs/remotes/satellite/master
should be spelled like
refs/remotes/origin/satellite/master
Signed-off-by: Brandon Casey <bcasey@nvidia.com> --- Documentation/git-push.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index fe46c42..a18f929 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -387,8 +387,8 @@ the ones in the examples below) can be configured as the default for `git push origin master:satellite/master dev:satellite/dev`:: Use the source ref that matches `master` (e.g. `refs/heads/master`) to update the ref that matches `satellite/master` (most probably - `refs/remotes/satellite/master`) in the `origin` repository, then - do the same for `dev` and `satellite/dev`. + `refs/remotes/origin/satellite/master`) in the `origin` repository, + then do the same for `dev` and `satellite/dev`. `git push origin HEAD:master`:: Push the current branch to the remote ref matching `master` in the
-- 1.7.8.4 ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------