doc: clarify how cp behaves with default ACLs

* doc/coreutils.texi (cp invocation): Mention that when copying files
without preserving permissions, the umask or a default ACL affect
the mode of new files.
* THANKS.in: Remove committer.
Related to http://bugs.gnu.org/8527

diff --git a/THANKS.in b/THANKS.in
index 776b4fbafd61e8ac18988835d801951424efe8b8..ba8e264b767094dca2a7cba94163ca1c23ecdf9a 100644 (file)
--- a/THANKS.in
+++ b/THANKS.in
@@ -47,7 +47,6 @@ Anders Kaseorg                      andersk@mit.edu
 Andi Kleen                          freitag@alancoxonachip.com
 Andre Novaes Cunha                  Andre.Cunha@br.global-one.net
 Andreas Frische                     andreasfrische@gmail.com
-Andreas Gruenbacher                 ag@bestbits.at
 Andreas Jaeger                      jaeger@gnu.org
 Andreas Luik                        luik@isa.de
 Andreas Stolcke                     stolcke@ICSI.Berkeley.EDU

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 4b37aefdc044ba5475825005fcfa1a4ca835109d..fa1592c97cfde609f0610300e7a4f0688927de04 100644 (file)
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -8052,9 +8052,11 @@ Using @option{--preserve} with no @var{attribute_list} is equivalent
 to @option{--preserve=mode,ownership,timestamps}.
 
 In the absence of this option, the permissions of existing destination
-files are unchanged, while each new file is created with the
-mode bits of the corresponding source file, minus the bits set in the
-umask and minus the set-user-ID and set-group-ID bits.
+files are unchanged.  Each new file is created with the mode of the
+corresponding source file minus the set-user-ID, set-group-ID, and
+sticky bits as the create mode; the operating system then applies either
+the umask or a default ACL, possibly resulting in a more restrictive
+file mode.
 @xref{File permissions}.
 
 @item --no-preserve=@var{attribute_list}