From 88e491044bf802e433a94a01401c342c287d9c24 Mon Sep 17 00:00:00 2001 From: Andreas Gruenbacher Date: Mon, 13 Apr 2015 01:41:50 +0200 Subject: 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 --- doc/coreutils.texi | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 4b37aefdc..fa1592c97 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} -- cgit v1.2.3-54-g00ecf