bekucera/coreutils
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/coreutils.git synced 2025-09-10 07:59:52 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: clarify how cp behaves with default ACLs

Browse Source 
* 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
This commit is contained in:
Andreas Gruenbacher
2015-04-13 01:41:50 +02:00
committed by Pádraig Brady
parent 1b1c40e1d6
commit 88e491044b
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
THANKS.in
View File

@@ -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

8
doc/coreutils.texi
View File

@@ -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}