demerphq <demerphq@xxxxxxxxx> writes: > And actually I find your use of "git pull" and "pull" in the > expression "pull from a branch other than one with the same name" > confusing. Barring misconfiguration pull operates on only one local > branch and it is usually the one with the same name. However push > operates on multiple local branches. It does with push.default = matching, but with either options we are discussing here, argumentless "git push" would push only one branch. The choice we have is whether to push to the branch with the same name, or to the branch from which "git pull" would take the changes. (I realize that in this discussion, "current" may be misleading. I mean "push.default=current", not "the behavior we have currently") > Lastly I have never really encountered any confusion with explaining > the default behaviour of git-fetch, nor actually git-pull, but I have > encountered lots of confusion of people using git-push. They expect > git-push to be the opposite of git-pull not git-fetch. I do also expect "git pull" to be symmetrical to "git pull", and "push.default=upstream" is the closest to symmetry. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html