summaryrefslogtreecommitdiff
path: root/rsync.yo
diff options
context:
space:
mode:
authorWayne Davison <wayned@samba.org>2008-02-18 14:10:13 -0800
committerWayne Davison <wayned@samba.org>2008-02-18 15:57:59 -0800
commit1ed56a05c26b6cb6f3891ce16be89aeab388a293 (patch)
tree52afcc200e3f4f3ba65b28afc95009bccfcbb885 /rsync.yo
parent28fb6365d096cf1e7125cde322c92c1b80b4ecee (diff)
downloadrsync-1ed56a05c26b6cb6f3891ce16be89aeab388a293.tar.gz
Extended the protocol-30 info-passing code at startup, and use it to
tell the client if the server can set the times on a symlink (both the server->client byte and the client->server use of -e). Make use of this info to allow the proper output of the 't' flag when rsync can set the time on a symlink (and we're talking protocol >= 30). Added output of "[no] symtimes" info in the --version message. Fixed the itemize.test so that it works when rsync believes that it can set the time of a symlink, but it can't really do it.
Diffstat (limited to 'rsync.yo')
-rw-r--r--rsync.yo4
1 files changed, 2 insertions, 2 deletions
diff --git a/rsync.yo b/rsync.yo
index 024df625..97582123 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -1681,8 +1681,8 @@ quote(itemization(
it() A bf(t) means the modification time is different and is being updated
to the sender's value (requires bf(--times)). An alternate value of bf(T)
means that the modification time will be set to the transfer time, which happens
- anytime a symlink is transferred, or when a regular file or device is
- transferred without bf(--times).
+ when a file/symlink/device is updated without bf(--times) and when a
+ symlink is changed and the receiver can't set its time.
it() A bf(p) means the permissions are different and are being updated to
the sender's value (requires bf(--perms)).
it() An bf(o) means the owner is different and is being updated to the