Skip to content

Commit 33405be

Browse files
jrngitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent a17a960 commit 33405be

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

Documentation/git-clone.txt

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,9 @@ DESCRIPTION
1919

2020
Clones a repository into a newly created directory, creates
2121
remote-tracking branches for each branch in the cloned repository
22-
(visible using `git branch -r`), and creates and checks out an initial
23-
branch equal to the cloned repository's currently active branch.
22+
(visible using `git branch -r`), and creates and checks out an
23+
initial branch that is forked from the cloned repository's
24+
currently active branch.
2425

2526
After the clone, a plain `git fetch` without arguments will update
2627
all the remote-tracking branches, and a `git pull` without

0 commit comments

Comments
 (0)