summaryrefslogtreecommitdiffstats
path: root/pull-fetch-param.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2007-01-02 00:04:15 +0000
committerJunio C Hamano <junio@hera.kernel.org>2007-01-02 00:04:15 +0000
commitb288d9efccdc870a87fa612f162eff891f26a71f (patch)
tree36ef915fff1dd53ad5b9677b1aacd6477cd3f8d6 /pull-fetch-param.txt
parentd3361ad1971d98f2e17e3bb09b77eee7b93700f0 (diff)
downloadgit-htmldocs-b288d9efccdc870a87fa612f162eff891f26a71f.tar.gz
Autogenerated HTML docs for v1.5.0-rc0-gf4bf2
Diffstat (limited to 'pull-fetch-param.txt')
-rw-r--r--pull-fetch-param.txt4
1 files changed, 0 insertions, 4 deletions
diff --git a/pull-fetch-param.txt b/pull-fetch-param.txt
index e852f41a3..8d4e950ab 100644
--- a/pull-fetch-param.txt
+++ b/pull-fetch-param.txt
@@ -39,10 +39,6 @@ checkout -b my-B remote-B`). Run `git fetch` to keep track of
the progress of the remote side, and when you see something new
on the remote branch, merge it into your development branch with
`git pull . remote-B`, while you are on `my-B` branch.
-The common `Pull: master:origin` mapping of a remote `master`
-branch to a local `origin` branch, which is then merged to a
-local development branch, again typically named `master`, is made
-when you run `git clone` for you to follow this pattern.
+
[NOTE]
There is a difference between listing multiple <refspec>