Junio C Hamano wrote:
>> # on branch master, derived from origin
>> $ git push ram
>> And branch.master.push is set to next? Will you let her shoot herself
>> in the foot like this?
> It is not shooting in the foot, if branch.master.push is explicitly
> set to update next. I do not see any issue in that part.
The question does not pertain to master being mapped to next; it
pertains to central-workflow versus triangular-workflow: origin versus
ram. If the user has set push.default to upstream, she _expects_
triangular pushes to always be denied, and this is the first violation
of that rule. I'm tilting towards building a dependency between
branch.<name>.push and push.default.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html