From: Pádraig Brady Date: Mon, 29 Jul 2013 08:51:52 +0000 (+0100) Subject: doc: clarify that cp by default doesn't adjust existing file perms X-Git-Tag: v8.22~92 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1127c8a009a28e04dd6a883e1ff59bbf02591583;p=thirdparty%2Fcoreutils.git doc: clarify that cp by default doesn't adjust existing file perms * doc/coreutils.texi (cp invocation): Mention explicitly what happens to permissions of existing files when -p is not specified. Fixes http://bugs.gnu.org/14972 --- diff --git a/doc/coreutils.texi b/doc/coreutils.texi index fb36866404..81bc97f091 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -8261,7 +8261,8 @@ all but @samp{Operation not supported} warnings are output. Using @option{--preserve} with no @var{attribute_list} is equivalent to @option{--preserve=mode,ownership,timestamps}. -In the absence of this option, each destination file is created with the +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. @xref{File permissions}.