A couple fixes in add_rule() for XFLG_ABS_IF_SLASH:

[rsync/rsync.git] / rsync.yo

diff --git a/rsync.yo b/rsync.yo
index 82b0fff..6bbf400 100644 (file)
--- a/rsync.yo
+++ b/rsync.yo
@@ -723,9 +723,12 @@ receiving user.
 dit(bf(--append)) This causes rsync to update a file by appending data onto
 the end of the file, which presumes that the data that already exists on
 the receiving side is identical with the start of the file on the sending
-side.  Any files that are the same size or longer on the receiving side
-are skipped.  Files that do not yet exist on the receiving side are
-transferred, regardless of size.  Implies bf(--inplace),
+side.  If a file needs to be transferred and its size on the receiver is
+the same or longer than the size on the sender, the file is skipped.  This
+does not interfere with the updating of a file's non-content attributes
+(e.g. permissions, ownership, etc.) when the file does not need to be
+transferred, nor does it affect the updating of any non-regular files.
+Implies bf(--inplace),
 but does not conflict with bf(--sparse) (since it is always extending a
 file's length).
 
@@ -1678,8 +1681,8 @@ quote(itemization(
   (requires bf(--checksum)) or that a symlink, device, or special file has
   a changed value.
   Note that if you are sending files to an rsync prior to 3.0.1, this
-  change flag will be present for checksum-differing regular files.
-  it() A bf(s) means the size of the file is different and will be updated
+  change flag will be present only for checksum-differing regular files.
+  it() A bf(s) means the size of a regular file is different and will be updated
   by the file transfer.
   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)