summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-03-03 09:24:11 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-03-03 09:24:11 (GMT)
commit4d0d0c3c59800e07d899e53121902833e3fd0cc7 (patch)
treed7740b10206a557b0abd9780044dd7081fa3820d
parent06d67b876642822828596b0b38cda2f61d438335 (diff)
downloadgit-1.8.2-rc2.zip
git-1.8.2-rc2.tar.gz
git-1.8.2-rc2.tar.bz2
Git 1.8.2-rc2v1.8.2-rc2
Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/RelNotes/1.8.2.txt30
-rwxr-xr-xGIT-VERSION-GEN2
2 files changed, 27 insertions, 5 deletions
diff --git a/Documentation/RelNotes/1.8.2.txt b/Documentation/RelNotes/1.8.2.txt
index 861ef02..78c6577 100644
--- a/Documentation/RelNotes/1.8.2.txt
+++ b/Documentation/RelNotes/1.8.2.txt
@@ -29,10 +29,15 @@ Many users found this counter-intuitive, given that "git commit -a"
and other commands operate on the entire tree regardless of where you
are. In this release, these commands give warning in such a case and
encourage the user to say "git add -u/-A ." instead when restricting
-the scope to the current directory. At Git 2.0 (not *this* one), we
-plan to change these commands without pathspec to operate on the
-entire tree, and training your fingers to type "." will protect you
-against the future change.
+the scope to the current directory.
+
+At Git 2.0 (not *this* one), we plan to change these commands without
+pathspec to operate on the entire tree. Forming a habit to type "."
+when you mean to limit the command to the current working directory
+will protect you against the planned future change, and that is the
+whole point of the new message (there will be no configuration
+variable to squelch this warning---it goes against the "habit forming"
+objective).
Updates since v1.8.1
@@ -463,3 +468,20 @@ details).
* Scripts to test bash completion was inherently flaky as it was
affected by whatever random things the user may have on $PATH.
+
+ * An element on GIT_CEILING_DIRECTORIES could be a "logical" pathname
+ that uses a symbolic link to point at somewhere else (e.g. /home/me
+ that points at /net/host/export/home/me, and the latter directory
+ is automounted). Earlier when Git saw such a pathname e.g. /home/me
+ on this environment variable, the "ceiling" mechanism did not take
+ effect. With this release (the fix has also been merged to the
+ v1.8.1.x maintenance series), elements on GIT_CEILING_DIRECTORIES
+ are by default checked for such aliasing coming from symbolic
+ links. As this needs to actually resolve symbolic links for each
+ element on the GIT_CEILING_DIRECTORIES, you can disable this
+ mechanism for some elements by listing them after an empty element
+ on the GIT_CEILING_DIRECTORIES. e.g. Setting /home/me::/home/him to
+ GIT_CEILING_DIRECTORIES makes Git resolve symbolic links in
+ /home/me when checking if the current directory is under /home/me,
+ but does not do so for /home/him.
+ (merge 7ec30aa mh/maint-ceil-absolute later to maint).
diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
index 7952039..6b96d6a 100755
--- a/GIT-VERSION-GEN
+++ b/GIT-VERSION-GEN
@@ -1,7 +1,7 @@
#!/bin/sh
GVF=GIT-VERSION-FILE
-DEF_VER=v1.8.2-rc1
+DEF_VER=v1.8.2-rc2
LF='
'