Blind wrote: > 2013/2/19 Ramkumar Ramachandra: >> No. I don't see why push.default is limiting. > > I just want to find a way to exclude a branch (or infact a group of > branches) from $git push --all. > so when I read your thing, I thought for a second that it could be a > possibility... But seems its not the case. What is your usecase? If you have a local branch with the same name as on the remote, why wouldn't you want to push-to-update it when you make changes in the branch? In other words, why doesn't push.default = matching suffice for most practical purposes. > ... or branch.<name>.pushremote can support some kind of a "none" value? Not a bad idea at all, provided you tell me your usecase. -- 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