summaryrefslogtreecommitdiff
path: root/git-compat-util.h
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2006-12-22 06:39:09 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-12-22 06:56:25 (GMT)
commitd41cb273d313a21979b05dba57d0c6b565b28ba6 (patch)
tree3bdfd6e084c4dc9b827b2e246124e23b9faf1ef9 /git-compat-util.h
parent27e4dd8de76bdd60c88003e0f27cee8ad26c5cd6 (diff)
downloadgit-d41cb273d313a21979b05dba57d0c6b565b28ba6.zip
git-d41cb273d313a21979b05dba57d0c6b565b28ba6.tar.gz
git-d41cb273d313a21979b05dba57d0c6b565b28ba6.tar.bz2
parse-remote: mark all refs not for merge only when fetching more than one
An earlier commit a71fb0a1 implemented much requested safety valve to refuse "git pull" or "git pull origin" without explicit refspecs from using the first set of remote refs obtained by reading .git/remotes/origin file or branch.*.fetch configuration variables to create a merge. The argument was that while on a branch different from the default branch, it is often wrong to merge the default remote ref suitable for merging into the master. That is fine as a theory. But many repositories already in use by people in the real world do not have any of the per branch configuration crap. They did not need it, and they do not need it now. Merging with the first remote ref listed was just fine, because they had only one ref (e.g. 'master' from linux-2.6.git) anyway. So this changes the safety valve to be a lot looser. When "git fetch" gets only one remote branch, the irritating warning would not trigger anymore. I think we could also make the warning trigger when branch.*.merge is not specified for the current branch, but is for some other branch. That is for another commit. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-compat-util.h')
0 files changed, 0 insertions, 0 deletions