Git 1.6.6-rc4
Hopefully the last rc before the final one. Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
@ -22,10 +22,10 @@ These changes were discussed long time ago and existing behaviours have
|
|||||||
been identified as more problematic to the userbase than keeping them for
|
been identified as more problematic to the userbase than keeping them for
|
||||||
the sake of backward compatibility.
|
the sake of backward compatibility.
|
||||||
|
|
||||||
When necessary, transition strategy for existing users has been designed
|
When necessary, a transition strategy for existing users has been designed
|
||||||
not to force them running around setting configuration variables and
|
not to force them running around setting configuration variables and
|
||||||
updating their scripts in order to either keep the traditional behaviour
|
updating their scripts in order to either keep the traditional behaviour
|
||||||
or adjust to the new behaviour on the day their sysadmin decides to install
|
or adjust to the new behaviour, on the day their sysadmin decides to install
|
||||||
the new version of git. When we switched from "git-foo" to "git foo" in
|
the new version of git. When we switched from "git-foo" to "git foo" in
|
||||||
1.6.0, even though the change had been advertised and the transition
|
1.6.0, even though the change had been advertised and the transition
|
||||||
guide had been provided for a very long time, the users procrastinated
|
guide 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
|
|||||||
repeating that unpleasantness in the 1.7.0 release.
|
repeating that unpleasantness in the 1.7.0 release.
|
||||||
|
|
||||||
For changes decided to be in 1.7.0, commands that will be affected
|
For changes decided to be in 1.7.0, commands that will be affected
|
||||||
have been much louder to strongly discourage such procrastination. If
|
have been much louder to strongly discourage such procrastination, and
|
||||||
you have been using recent versions of git, you would have seen
|
they continue to be in this release. If you have been using recent
|
||||||
warnings issued when you exercised features whose behaviour will
|
versions of git, you would have seen warnings issued when you used
|
||||||
change, with a clear instruction on how to keep the existing behaviour
|
features whose behaviour will change, with a clear instruction on how
|
||||||
if you want to. You hopefully are already well prepared.
|
to keep the existing behaviour if you want to. You hopefully are
|
||||||
|
already well prepared.
|
||||||
|
|
||||||
Of course, we have also been giving "this and that will change in
|
Of course, we have also been giving "this and that will change in
|
||||||
1.7.0; prepare yourselves" warnings in the release notes and
|
1.7.0; prepare yourselves" warnings in the release notes and
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
#!/bin/sh
|
#!/bin/sh
|
||||||
|
|
||||||
GVF=GIT-VERSION-FILE
|
GVF=GIT-VERSION-FILE
|
||||||
DEF_VER=v1.6.6-rc3.GIT
|
DEF_VER=v1.6.6-rc4.GIT
|
||||||
|
|
||||||
LF='
|
LF='
|
||||||
'
|
'
|
||||||
|
Reference in New Issue
Block a user