Patch-ID: bash40-001 Bash has problems parsing certain constructs inside Posix-style $(...) command substitutions, mostly with backslash-quoting and reserved word recognition. This is an issue because the contents are parsed at the time the word containing the command substitution is read. Patch-ID: bash40-002 A line inadvertenly omitted from a submitted patch results in core dumps when attempting filename completion while using the bash-completion package. Patch-ID: bash40-003 Under certain circumstances, constructs containing command substitutions prevent PS1 from being re-evaluated and updated before being displayed. Patch-ID: bash40-004 In some cases, enabling the `checkjobs' shell option will cause the shell to core dump when executing the `exit' builtin. Patch-ID: bash40-005 The `declare' builtin dumped core when attempting to assign associative array indices containing some special characters, even when they were quoted before being expanded. Patch-ID: bash40-006 Bash did not parse pipelines using the |& construct correctly if the pipeline elements were not simple commands. Patch-ID: bash40-007 Bash had a number of problems parsing associative array subscripts containing special characters. The subscripts are supposed to be read as if they are enclosed between double quotes. Patch-ID: bash40-008 (missing desription in the patch file) Bug-Reference-URL is http://lists.gnu.org/archive/html/bug-bash/2009-02/msg00230.html Patch-ID: bash40-009 When the read builtin returned due to a timeout supplied with the -t option, it did not restore any modified terminal attribtues. Patch-ID: bash40-010 Bash has problems parsing comments in case statements when they appear in $(...) subshells. Reproducible: Always Steps to Reproduce:
Reassigning to base-system herd.
those patches are just the ones we already have in bash-4.0, but this gives me an excuse to move into ~arch
