@matheusbsbs / matheus-bagliano / commits / db9819a40a
Fork 0

Documentation: update git-clone man page with new behavior

Update git-clone man page to reflect recent changes (--use-separate-remote default and use of .git/config instead of remotes files), and rewrite introduction. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Junio C Hamano <junkio@cox.net>

J. Bruce Fields committed Dec 8, 2006 at 01:27 UTC db9819a40a56b4747931e637c1c22a104dcab902
1 file changed +12 -13
Documentation/git-clone.txt
+12 -13
@@ -16,22 +16,21 @@ SYNOPSIS
16
17 DESCRIPTION
18 -----------
19 -Clones a repository into a newly created directory. All remote
20 -branch heads are copied under `$GIT_DIR/refs/heads/`, except
21 -that the remote `master` is also copied to `origin` branch.
19
23 -In addition, `$GIT_DIR/remotes/origin` file is set up to have
24 -this line:
20 +Clones a repository into a newly created directory, creates
21 +remote-tracking branches for each branch in the cloned repository
22 +(visible using `git branch -r`), and creates and checks out a master
23 +branch equal to the cloned repository's master branch.
24
26 - Pull: master:origin
27 -
28 -This is to help the typical workflow of working off of the
29 -remote `master` branch. Every time `git pull` without argument
30 -is run, the progress on the remote `master` branch is tracked by
31 -copying it into the local `origin` branch, and merged into the
32 -branch you are currently working on. Remote branches other than
33 -`master` are also added there to be tracked.
25 +After the clone, a plain `git fetch` without arguments will update
26 +all the remote-tracking branches, and a `git pull` without
27 +arguments will in addition merge the remote master branch into the
28 +current branch.
29
30 +This default configuration is achieved by creating references to
31 +the remote branch heads under `$GIT_DIR/refs/remotes/origin` and
32 +by initializing `remote.origin.url` and `remote.origin.fetch`
33 +configuration variables.
34
35 OPTIONS
36 -------