commit bash-20060706 snapshotbash-3.2-alpha

1 files changed, 16 insertions, 1 deletions

diff --git a/COMPAT b/COMPAT
index df64c03d..8ea9339b 100644
--- a/COMPAT
+++ b/COMPAT
@@ -1,5 +1,5 @@
 This document details the incompatibilities between this version of bash,
-bash-3.1, and the previous widely-available versions, bash-1.14 (which is
+bash-3.2, and the previous widely-available versions, bash-1.14 (which is
 still the `standard' version for a few Linux distributions) and bash-2.x. 
 These were discovered by users of bash-2.x and 3.x, so this list is not
 comprehensive.  Some of these incompatibilities occur between the current
@@ -256,3 +256,18 @@ bash-2.0 were significant.)
 
 30. Beginning with bash-3.1, the combination of posix mode and enabling the
     `xpg_echo' option causes echo to ignore all options, not looking for `-n'
+
+31. Beginning with bash-3.2, bash follows the Bourne-shell-style (and POSIX-
+    style) rules for parsing the contents of old-style backquoted command
+    substitutions.  Previous versions of bash attempted to recursively parse
+    embedded quoted strings and shell constructs; bash-3.2 uses strict POSIX
+    rules to find the closing backquote and simply passes the contents of the
+    command substitution to a subshell for parsing and execution.
+
+32. Beginning with bash-3.2, bash uses access(2) when executing primaries for
+    the test builtin and the [[ compound command, rather than looking at the
+    file permission bits obtained with stat(2).  This obeys restrictions of
+    the file system (e.g., read-only or noexec mounts) not available via stat.
+
+33. Beginning with bash-3.1/readline-5.1, the readline key binding code obeys
+    the current setting of the `convert-meta' variable.