From: Jim Meyering <jim@meyering.net>
Date: Fri, 24 Jun 2005 08:05:51 +0000 (+0000)
Subject: (cp invocation): Clarify how --reply=no works.
X-Git-Tag: CPPI-1_12~493
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a8249aba924e887d50ab0a93867b0b8c061f31c4;p=thirdparty%2Fcoreutils.git

(cp invocation): Clarify how --reply=no works.
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 3af02df2a6..8e69b726d0 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -6515,6 +6515,10 @@ given as a response to every prompt about a destination file.  That effectively
 cancels any preceding @option{--interactive} or @option{-i} option.
 Specify @option{--reply=no} to make @command{cp} act as if @samp{no} were
 given as a response to every prompt about a destination file.
+Note that @option{--reply=no} has an effect only when mv would prompt
+without @option{-i} or equivalent, i.e., when a destination file exists and is
+not writable, standard input is a terminal, and no @option{-f} (or equivalent)
+option is specified.
 Specify @option{--reply=query} to make @command{cp} prompt the user
 about each existing destination file.