Stefan Beller <sbel...@google.com> writes: >> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt >> index 0a639664fd..1fa01210a2 100644 >> --- a/Documentation/git-push.txt >> +++ b/Documentation/git-push.txt >> @@ -212,8 +212,9 @@ must not already exist. >> + >> Note that all forms other than `--force-with-lease=<refname>:<expect>` >> that specifies the expected current value of the ref explicitly are >> -still experimental and their semantics may change as we gain experience > > This indicates that this feature is not 'experimental' any more, but disabled > (for safety reasons as described below). This implies we will not change the > heuristic for push.allowLazyForceWithLease easily.
I actually wanted to say it was a failed experiment, but I see your point. Let's leave the "still experimental" label. >> test_expect_success 'push to update (protected)' ' >> @@ -78,7 +79,6 @@ test_expect_success 'push to update (protected, tracking, >> forced)' ' >> ( >> cd dst && >> test_commit E && >> - git ls-remote . refs/remotes/origin/master >expect && > > This seems unrelated, so ideally it is a separate commit? Yes, I looked for other things that may be good to fix while at it, and planned to make a separate clean-up patch if I found enough, but this was the only one. >> @@ -91,6 +91,7 @@ test_expect_success 'push to update (allowed)' ' >> ( >> cd dst && >> test_commit D && >> + git config push.allowLazyForceWithLease false && > > Here I thought > > test_config -C dst ... > > at the beginning might be useful, though .. I did not think test_config would work inside a subshell.
