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

(usage): Clarify how --reply=no works.
---

diff --git a/src/mv.c b/src/mv.c
index 490e57c06d..a56aa4fd5c 100644
--- a/src/mv.c
+++ b/src/mv.c
@@ -317,7 +317,12 @@ Mandatory arguments to long options are mandatory for short options too.\n\
 "), stdout);
       fputs (_("\
       --reply={yes,no,query}   specify how to handle the prompt about an\n\
-                                 existing destination file\n\
+                                 existing destination file.  Note that\n\
+                                 --reply=no has an effect only when mv\n\
+                                 would prompt without -i or equivalent, i.e.,\n\
+                                 when a destination file exists and is not\n\
+                                 writable, standard input is a terminal, and\n\
+                                 no -f (or equivalent) option is specified\n\
       --strip-trailing-slashes remove any trailing slashes from each SOURCE\n\
                                  argument\n\
   -S, --suffix=SUFFIX          override the usual backup suffix\n\