From: Pádraig Brady <P@draigBrady.com>
Date: Sun, 10 Dec 2017 00:18:00 +0000 (-0800)
Subject: doc: clarify that cp --force may recreate files
X-Git-Tag: v8.29~18
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f17c1df3919d66fd1e71057070604f9af6d4bcc5;p=thirdparty%2Fcoreutils.git

doc: clarify that cp --force may recreate files

* doc/coreutils.texi (cp invocation): The language used
to describe recreating the file was a little confusing
as it mentioned opening a removed file.
Fixes https://bugs.gnu.org/29315
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 09730f6d34..ed3a63308e 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -8520,8 +8520,9 @@ Equivalent to @option{--no-dereference --preserve=links}.
 @opindex --force
 When copying without this option and an existing destination file cannot
 be opened for writing, the copy fails.  However, with @option{--force},
-when a destination file cannot be opened, @command{cp} then removes it and
-tries to open it again.  When this option is combined with
+when a destination file cannot be opened, @command{cp} then
+tries to recreate the file by first removing it.
+When this option is combined with
 @option{--link} (@option{-l}) or @option{--symbolic-link}
 (@option{-s}), the destination link is replaced, and unless
 @option{--backup} (@option{-b}) is also given there is no brief