Re: [PATCH] push: add config option to --force-with-lease by default.
- From
Francesco Mazzoli <f@mazzo.li>
- Date
- Jul 5, 2017, 06:34 UTC
- Message-ID
- <CAPB=P5xsssm=RiAkEuAtpxe52+-sNAPVP2qnQGctLjNZFYznkg@mail.gmail.com>
- In-Reply-To
- <xmqqvan8jdje.fsf@gitster.mtv.corp.google.com>
On 4 July 2017 at 19:51, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> People have been burned by the lazy "--force-with-lease" that does > not say what object to expect there and forces the command to DWIM > incorrectly what the remote's ref ought to be pointing at. This > change encourages its use without the user being painfully aware of > that danger. Whenever you say "push --force", you'd be using the > dangerous "--force-with-lease" that does not specify what the > expected current state of the remote is. The end result gives an > illusion of being safer than a simple "--force", without being > not really safer.
Could you clarify the danger you're referring to? E.g. give an example of surprising --force-with-lease behavior that we do not want to encourage?
Thanks, Francesco