[PATCH] Describe git-clone's actual behavior in the summary

From: Steven Grimm <koreth@midwinter.com>
Date: Jan 6, 2007, 01:52 UTC
Message-ID: <459F00D4.3040203@midwinter.com>

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>
---
 Documentation/git-clone.txt |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index e7085fd..a782074 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -18,13 +18,13 @@ DESCRIPTION
 
 Clones a repository into a newly created directory, creates
 remote-tracking branches for each branch in the cloned repository
-(visible using `git branch -r`), and creates and checks out a master
-branch equal to the cloned repository's master branch.
+(visible using `git branch -r`), and creates and checks out an initial
+branch equal to the cloned repository's currently active branch.
 
 After the clone, a plain `git fetch` without arguments will update
 all the remote-tracking branches, and a `git pull` without
 arguments will in addition merge the remote master branch into the
-current branch.
+current master branch, if any.
 
 This default configuration is achieved by creating references to
 the remote branch heads under `$GIT_DIR/refs/remotes/origin` and

-- 
1.5.0.rc0.g244a7