@matheusbsbs / matheus-bagliano / commits / 955289bf92
Fork 0

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>

Andy Parkins committed Dec 6, 2006 at 12:07 UTC 955289bf92f0513377763c9aacfe426d5151b05a
1 file changed +3 -1
git-clone.sh
+3 -1
@@ -400,7 +400,9 @@ then
400 rm -f "refs/remotes/$origin/HEAD"
401 git-symbolic-ref "refs/remotes/$origin/HEAD" \
402 "refs/remotes/$origin/$head_points_at"
403 - esac
403 + esac &&
404 + git-repo-config branch."$head_points_at".remote "$origin" &&
405 + git-repo-config branch."$head_points_at".merge "refs/heads/$head_points_at"
406 esac
407
408 case "$no_checkout" in