Describe git-clone's actual behavior in the summary
If a branch other than "master" is checked out in the origin repository, git-clone makes a local copy of that branch rather than the origin's "master" branch. This patch describes the actual behavior. Signed-off-by: Steven Grimm <koreth@midwinter.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
Steven Grimm committed
Jan 5, 2007 at 17:52 UTC
1170e8026ae507c510619fceff969b1cf2900a28
1 file changed
+3
-3
Documentation/git-clone.txt
+3
-3
@@ -18,13 +18,13 @@ DESCRIPTION
18
19
Clones a repository into a newly created directory, creates
20
remote-tracking branches for each branch in the cloned repository
21
-(visible using `git branch -r`), and creates and checks out a master
22
-branch equal to the cloned repository's master branch.
21
+(visible using `git branch -r`), and creates and checks out an initial
22
+branch equal to the cloned repository's currently active branch.
23
24
After the clone, a plain `git fetch` without arguments will update
25
all the remote-tracking branches, and a `git pull` without
26
arguments will in addition merge the remote master branch into the
27
-current branch.
27
+current master branch, if any.
28
29
This default configuration is achieved by creating references to
30
the remote branch heads under `$GIT_DIR/refs/remotes/origin` and