summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2023-01-31 09:24:43 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2023-01-31 09:25:25 -0800
commit01503ce7319b099d9deaeab43628e1b2b07a874a (patch)
treebf8849754c05d2e92ed274a688755081a7952c15 /doc
parent7a69df88999bedd8e9fccf9f3dfa9ac6907fab66 (diff)
downloadcoreutils-01503ce7319b099d9deaeab43628e1b2b07a874a.tar.gz
cp,mv: skipping due to -u is success, not failure
This reverts the previous change, so that when a file is skipped due to -u, this is not considered a failure. * doc/coreutils.texi: Document this. * src/copy.c (copy_internal): If --update says to skip, treat this as success instead of failure. * tests/mv/update.sh, tests/cp/slink-2-slink.sh: Revert previous change, to match reverted behavior.
Diffstat (limited to 'doc')
-rw-r--r--doc/coreutils.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index da73503ed..143b93de9 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -9191,8 +9191,8 @@ results in an error message on systems that do not support symbolic links.
@opindex --update
@cindex newer files, copying only
Do not copy a non-directory that has an existing destination with the
-same or newer modification timestamp; silently fail instead.
-If timestamps are being preserved,
+same or newer modification timestamp; instead, silently skip the file
+without failing. If timestamps are being preserved,
the comparison is to the source timestamp truncated to the
resolutions of the destination file system and of the system calls
used to update timestamps; this avoids duplicate work if several
@@ -10124,7 +10124,8 @@ fail with a diagnostic instead of copying and then removing the file.
@opindex --update
@cindex newer files, moving only
Do not move a non-directory that has an existing destination with the
-same or newer modification timestamp; silently fail instead.
+same or newer modification timestamp;
+instead, silently skip the file without failing.
If the move is across file system boundaries, the comparison is to the
source timestamp truncated to the resolutions of the destination file
system and of the system calls used to update timestamps; this avoids