Explicitly add the default "git pull" behaviour to .git/config on clone
authorAndy Parkins <andyparkins@gmail.com>
Wed, 6 Dec 2006 12:07:23 +0000 (12:07 +0000)
committerJunio C Hamano <junkio@cox.net>
Wed, 6 Dec 2006 19:24:04 +0000 (11:24 -0800)
commit955289bf92f0513377763c9aacfe426d5151b05a
treeef1b389c0b108464b7cd1d098fa3de0575a3ecc5
parentde51faf3888505fa3d661d4c35f32ecaf9fa1087
Explicitly add the default "git pull" behaviour to .git/config on clone

Without any specification in the .git/config file, git-pull will execute
"git-pull origin"; which in turn defaults to pull from the first "pull"
definition for the remote, "origin".

This is a difficult set of defaults to track for a new user, and it's
difficult to see what tells git to do this (especially when it is
actually hard-coded behaviour).  To ameliorate this slightly, this patch
explicitly specifies the default behaviour during a clone using the
"branch" section of the config.

For example, a clone of a typical repository would create a .git/config
containing:
  [remote "origin"]
  url = proto://host/repo.git
  fetch = refs/heads/master:refs/remotes/origin/master
  [branch "master"]
  remote = origin
  merge = refs/heads/master

The [branch "master"] section is such that there is no change to the
functionality of git-pull, but that functionality is now explicitly
documented.

Signed-off-by: Andy Parkins <andyparkins@gmail.com>
git-clone.sh