* Major changes in release 4.5.12, 2013-09-22

** Functional Changes to find

The GNU extension "find ... -perm /MODE" is no longer disabled when
the POSIXLY_CORRECT environment variable is set.

The obsolete GNU extension "find ... -perm +MODE", which was withdrawn
in release 4.2.21 in 2005 due to compatibility problems, has been
completely removed.  Use "find ... -perm /MODE" instead.

** Documentation Changes

If you use -type or -xtype with a type letter corresponding to a file
type which is not supported by the system on which find was compiled,
find will now give a clearer error message (though the functionality
is unchanged).  Type letters are affected are D, l and p (for Solaris
Doors, symbolic links and named pipes respectively).

The output of xargs --help has been slightly changed for greater
clarity.

The documentation for xargs now warns about parallel processes (xargs
-P) sharing stdout.

The documentation for find -execdir now describes correctly that the
command will be executed in the same directory as the file we were
considering at the time.  The documentation previously (and
incorrectly) stated that the original working directory of find would
be used.

** Bug Fixes

Some bugs in 4.5.11 were fixed without adding them to the bug
database, though they are in the ChangeLog:

*** Use of [[ ... ]] in find/testsuite/sv-bug-32043.sh

*** Don't delete header files in "lib/" for "make clean".

*** xargs: wait for process before prompting in interactive mode (-p)

These following fixed bugs are recorded at
https://savannah.gnu.org/bugs/?group=findutils:

#40088: potential buffer overflow in -execdir and -okdir

#39324: exits without error on OOM

#38583: errno-buffer read failed in xargs_do_exec

#38474: Unintended (?) behaviour change of -perm +mode predicate

#36652: Better document that -0/-d turns off the effect of -E.

#34976: find -execdir leaks file descriptors for the working directory