+ BUG FIXES:
+
+ - Restore the list-clearing behavior of "!" in a .cvsignore file (2.6.3
+ was only treating it as a special token in an rsync include/exclude
+ file).
+
+ - The combination of --verbose and --dry-run now mentions changes in
+ directories and it now includes the full update information that
+ would be output without --dry-run at higher levels of verbosity.
+
+ - Avoid a mkdir warning when removing a directory in the destination
+ that already exists in the --backup-dir.
+
+ - An OS that has a binary mode for its files (such as cygwin0 needed
+ setmode(fd, O_BINARY) called on the temp-file we opened with
+ mkstemp(). (Fix derived from the cygwin's rsync package.)
+
+ - Fixed a potential hang when verbosity is high, the client side is
+ the sender, and the file-list is large.
+
+ - We now check if the OS doesn't support using mknod() for creating
+ FIFOs and sockets, and compile-in using mkfifo() and socket() when
+ necessary.
+
+ - Fixed an off-by-one error in the handling of --max-delete=N.
+
+ - One place in the code wasn't checking if fork() failed.
+
+ - The "ignore nonreadable" daemon parameter no longer affects symlinks
+ that are being copied, even if they point nowhere.
+
+ - If the OS does not have lchown() and its chown() tries to set the
+ referent of a symlink (as it should), we no longer try to set the
+ user and group of a symlink.
+
+ - The generator now properly runs the hard-link loop and the dir-time
+ rewriting loop after we're sure that the redo phase is complete.
+
+ - When --backup was specified with --partial-dir=DIR (where DIR is a
+ relative path), the backup code was erroneously trying to backup a
+ file that was put into the partial-dir.
+
+ - One call to flush_write_file() was not being checked for an error.
+
+ - The --no-relative option was not being sent from the client to a
+ server sender.
+
+ - If an rsync daemon specified "dont compress = ..." for a file and the
+ client tried to specify --compress, the libz code was not handling a
+ compression level of 0 properly. This could cause a transfer failure
+ if the block-size for a file was large enough (i.e. rsync might have
+ exited with an error for large files).
+
+ - If a daemon can't open the specified log file (i.e. syslog is not
+ being used), die without crashing. We also try to output an error
+ about the failure (which will only be seen if --no-detach was
+ specified).
+
+ - A local transfer no longer duplicates all its include/exclude options
+ by sending the forked process a copy of the list it already has.
+
+ ENHANCEMENTS:
+
+ - Rsync now supports popt's option aliases, which means that you can
+ use /etc/popt and/or ~/.popt to create your own option aliases.
+
+ - Added the --delete-during (--del) option which will delete files
+ from on the receiving side incrementally as each directory in the
+ transfer is being processed (which makes it more efficient than the
+ default, before-the-transfer behavior of --delete). Note that the
+ --del option is implemented as an internally-defined popt alias, so
+ an rsync daemon that refuses "delete" (which, for safety's sake,
+ really matches "delete*") will still refuse all delete options. The
+ default --delete behavior is also explicitly selectable via
+ --delete-before.
+
+ - All the --delete-WHEN options are now more memory efficient:
+ Previously an entire duplicate set of file-list objects was created
+ on the receiving side for the entire destination hierarchy. The new
+ algorithm only creates one directory of objects at a time.
+
+ - Added the --copy-dest option, which works like --link-dest except
+ that it includes copies of identical files.
+
+ - Added support for specifying multiple --compare-dest, --copy-dest, or
+ --link-dest options, but only of a single type. (Promoted from the
+ patches dir and enhanced.)
+
+ - Added the --max-size option. (Promoted from the patches dir.)
+
+ - The daemon-mode options were separated from the normal rsync options
+ so that they can't be mixed together. This makes it impossible to
+ start a daemon that had improper default option values that could
+ cause problems (such as a hang or an abort) when a client connects.
+
+ - The --bwlimit option may now be used in combination with --daemon
+ to specify both a default value for the daemon side and a value
+ that cannot be exceeded by a user-specified --bwlimit option.