From: Andreas Gruenbacher Date: Sun, 12 Apr 2015 23:41:50 +0000 (+0200) Subject: doc: clarify how cp behaves with default ACLs X-Git-Tag: v8.24~86 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=88e491044bf802e433a94a01401c342c287d9c24;p=thirdparty%2Fcoreutils.git 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 776b4fbafd..ba8e264b76 100644 --- 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 4b37aefdc0..fa1592c97c 100644 --- 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}