Peter Krefting wrote: > I know the policy in Git is to not allow the remote repository > dictate anything about the configuration in the local repository, > but as an alternative to changing the "push.default" value, perhaps > we should allow setting some configuration option on the remote > repository that blocks it from being the target of a "push.default = > matching" push? If I work for your company and always keep all my local topic branches in good order, I would expect to be permitted to use "push.default = matching" to easily push them all at once after I have finished preparing them, provided I have set up my local copy of git that way explicitly, regardless of what the person setting up the infrastructure thought. What would I be missing? Curious, Jonathan -- 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