- * Fixed a bug in the handling of -H (hard-links) that might
- cause the expanded PATH/NAME value of the current item to
- get overwritten (due to an expanded-name caching bug).
-
- * We now reset the "new data has been sent" flag at the start
- of each file we send. This makes sure that an interrupted
- transfer with the --partial option set doesn't keep a shorter
- temp file than the current basis file when no new data has been
- transfered over the wire for that file.
+ - Files specified in the daemon's "exclude" or "exclude from" config
+ items are now excluded from being uploaded (assuming that the module
+ allows uploading at all) in addition to the old download exclusion.
+
+ - Got rid of a potential hang in the receiver when near the end of a
+ phase.
+
+ - When using --backup without a --backup-dir, rsync no longer preserves
+ the modify time on directories. This avoids confusing NFS.
+
+ - When --copy-links (-L) is specified, we now output a separate error
+ for a symlink that has no referent instead of claiming that a file
+ "vanished".
+
+ - The --copy-links (-L) option no longer has the side-effect of telling
+ the receiving side to follow symlinks. See the --keep-dirlinks
+ option (mentioned below) for a way to specify that behavior.
+
+ - Error messages from the daemon server's option-parsing (such as
+ refused options) are now successfully transferred back to the client
+ (the server used to fail to send the message because the socket
+ wasn't in the right state for the message to get through).
+
+ - Most transfer errors that occur during a daemon transfer are now
+ returned to the user in addition to being logged (some messages are
+ intended to be daemon-only and are not affected by this).
+
+ - Fixed a bug in the daemon authentication code when using one of the
+ batch-processing options.
+
+ - We try to work around some buggy IPv6 implementations that fail to
+ implement IPV6_V6ONLY. This should fix the "address in use" error
+ that some daemons get when running on an OS with a buggy IPv6
+ implementation. Also, if the new code gets this error, we might
+ suggest that the user specify --ipv4 or --ipv6 (if we think it will
+ help).
+
+ - When the remote rsync dies, make a better effort to recover any error
+ messages it may have sent before dying (the local rsync used to just
+ die with a socket-write error).
+
+ - When using --delete and a --backup-dir that contains files that are
+ hard-linked to their destination equivalents, rsync now makes sure
+ that removed files really get removed (avoids a really weird rename()
+ behavior).