@@ -22,10 +22,10 @@ These changes were discussed long time ago and existing behaviours have
2222been identified as more problematic to the userbase than keeping them for
2323the sake of backward compatibility.
2424
25- When necessary, transition strategy for existing users has been designed
25+ When necessary, a transition strategy for existing users has been designed
2626not to force them running around setting configuration variables and
2727updating their scripts in order to either keep the traditional behaviour
28- or adjust to the new behaviour on the day their sysadmin decides to install
28+ or adjust to the new behaviour, on the day their sysadmin decides to install
2929the new version of git. When we switched from "git-foo" to "git foo" in
30301.6.0, even though the change had been advertised and the transition
3131guide had been provided for a very long time, the users procrastinated
@@ -34,11 +34,12 @@ their sysadmins updated their git installation. We are trying to avoid
3434repeating that unpleasantness in the 1.7.0 release.
3535
3636For changes decided to be in 1.7.0, commands that will be affected
37- have been much louder to strongly discourage such procrastination. If
38- you have been using recent versions of git, you would have seen
39- warnings issued when you exercised features whose behaviour will
40- change, with a clear instruction on how to keep the existing behaviour
41- if you want to. You hopefully are already well prepared.
37+ have been much louder to strongly discourage such procrastination, and
38+ they continue to be in this release. If you have been using recent
39+ versions of git, you would have seen warnings issued when you used
40+ features whose behaviour will change, with a clear instruction on how
41+ to keep the existing behaviour if you want to. You hopefully are
42+ already well prepared.
4243
4344Of course, we have also been giving "this and that will change in
44451.7.0; prepare yourselves" warnings in the release notes and
0 commit comments