summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2009-12-20 20:15:02 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-12-20 20:15:02 (GMT)
commitab0964d951e4ea88f9ea2cbb88388c1bcd4ae911 (patch)
treec16bb7744310bbe8266f1060a19ea8342dab8f5a
parentb6b9f83ea19de3a98ca8466977aac2dc0bc03626 (diff)
downloadgit-ab0964d951e4ea88f9ea2cbb88388c1bcd4ae911.zip
git-ab0964d951e4ea88f9ea2cbb88388c1bcd4ae911.tar.gz
git-ab0964d951e4ea88f9ea2cbb88388c1bcd4ae911.tar.bz2
Git 1.6.6-rc4v1.6.6-rc4
Hopefully the last rc before the final one. Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/RelNotes-1.6.6.txt15
-rwxr-xr-xGIT-VERSION-GEN2
2 files changed, 9 insertions, 8 deletions
diff --git a/Documentation/RelNotes-1.6.6.txt b/Documentation/RelNotes-1.6.6.txt
index b9e8642..72df781 100644
--- a/Documentation/RelNotes-1.6.6.txt
+++ b/Documentation/RelNotes-1.6.6.txt
@@ -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
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
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
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
@@ -34,11 +34,12 @@ their sysadmins updated their git installation. We are trying to avoid
repeating that unpleasantness in the 1.7.0 release.
For changes decided to be in 1.7.0, commands that will be affected
-have been much louder to strongly discourage such procrastination. If
-you have been using recent versions of git, you would have seen
-warnings issued when you exercised features whose behaviour will
-change, with a clear instruction on how to keep the existing behaviour
-if you want to. You hopefully are already well prepared.
+have been much louder to strongly discourage such procrastination, and
+they continue to be in this release. If you have been using recent
+versions of git, you would have seen warnings issued when you used
+features whose behaviour will change, with a clear instruction on how
+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
1.7.0; prepare yourselves" warnings in the release notes and
diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
index 039e8d4..22f2461 100755
--- a/GIT-VERSION-GEN
+++ b/GIT-VERSION-GEN
@@ -1,7 +1,7 @@
#!/bin/sh
GVF=GIT-VERSION-FILE
-DEF_VER=v1.6.6-rc3.GIT
+DEF_VER=v1.6.6-rc4.GIT
LF='
'