Mention local-only effect of --msgs2stderr.

diff --git a/rsync.yo b/rsync.yo
index 20300eb9cd4c8596c6e494a6c478fd497ae88ab0..a2aae209d46f3353f5c88b6dcb8fc8bee02e164d 100644 (file)
--- a/rsync.yo
+++ b/rsync.yo
@@ -571,7 +571,9 @@ directly to stderr rather than to send messages to the client side via the
 protocol (which normally outputs info messages via stdout).  This is mainly
 intended for debugging in order to avoid changing the data sent via the
 protocol, since the extra protocol data can change what is being tested.
-Keep in mind that a daemon connection does not have a stderr channel to send
+The option does not affect the remote side of a transfer without using
+bf(--remote-option) -- e.g. bf(-M--msgs2stderr).
+Also keep in mind that a daemon connection does not have a stderr channel to send
 messages back to the client side, so if you are doing any daemon-transfer
 debugging using this option, you should start up a daemon using bf(--no-detach)
 so that you can see the stderr output on the daemon side.