Re: Please discuss: what "git push" should do when you do not say what to push?
From: Martin Langhoff <hidden>
Date: 2016-06-15 22:53:20
On Sat, Mar 17, 2012 at 1:22 AM, Junio C Hamano [off-list ref] wrote:
If the conclusion of the discussion is that we will change the default, the transition to the new default will go like this:
I am in general agreement with the course of action outlined. There is one little thing I had expected in addition, that is not discussed: --force should change behaviour, immediately, to "current" or even none (forcing the user to name the remote and branch explicitly). The potential for messups with --force combined with "matching" and a repo that allows it is considerable. And I cannot imagine any mainstream use cases for --force defaulting to matching; at least none important enough to counterbalance the damage. cheers, m -- martin.langhoff@gmail.com martin@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff