aboutsummaryrefslogtreecommitdiff
path: root/git-pull.sh
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2009-10-09 18:07:39 -0500
committerJunio C Hamano <gitster@pobox.com>2009-10-09 17:21:46 -0700
commit33405be34bcb72d8fe69463c80c542eacb19b7ef (patch)
tree06a548e2ab557dca79f97bc45a964aa81f6e5275 /git-pull.sh
parenta17a9606e49dd3ad08558706f85475a694deb68b (diff)
downloadgit-33405be34bcb72d8fe69463c80c542eacb19b7ef.tar.gz
git-33405be34bcb72d8fe69463c80c542eacb19b7ef.tar.xz
Documentation: clone: clarify discussion of initial branch
When saying the initial branch is equal to the currently active remote branch, it is probably intended that the branch heads point to the same commit. Maybe it would be more useful to a new user to emphasize that the tree contents and history are the same. More important, probably, is that this new branch is set up so that "git pull" merges changes from the corresponding remote branch. The next paragraph addresses that directly. What the reader needs to know to begin with is that (1) the initial branch is your own; if you do not pull, it won't get updated, and that (2) the initial branch starts out at the same commit as the upstream. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-pull.sh')
0 files changed, 0 insertions, 0 deletions