- - Added the --append option that makes rsync append data onto files
- that are longer on the source than the destination (this includes new
- files).
-
- - Added the --min-size=SIZE option to exclude small files from the
- transfer.
-
- - Added the --compress-level option to allow you to set how aggressive
- rsync's compression should be (the option implies --compress).
-
- - Enhanced the parsing of the SIZE value for --min-size and --max-size.
-
- - If lutimes() and/or lchmod() are around, use them to allow the
- preservation of attributes on symlinks.
-
- - Added two config items to the rsyncd.conf parsing: "pre-xfer exec"
- and "post-xfer exec". These allow a command to be specified on a
- per-module basis that will be run before and/or after a daemon-mode
- transfer.
-
- - When using the --relative option, you can now insert a dot dir in
- the source path to indicate where the replication of the source dirs
- should start. For example, if you specify a source path of
- rsync://host/module/foo/bar/./baz/dir with -R, rsync would only
- replicate the "baz/dir" part of the source path (note: a trailing
- dot dir is unaffected unless it also has a trailing slash).
+ - A new incremental-recursion algorithm is now used when rsync is talking
+ to another 3.0.0 version. This starts the transfer going more quickly
+ (before all the files have been found), and requires much less memory.
+ See the --recursive option in the manpage for some restrictions.
+
+ - The default --delete algorithm is now --delete-during when talking to a
+ 3.x rsync. This is a faster scan than using --delete-before (which is
+ the default when talking to older rsync versions), and is compatible
+ with the new incremental recursion mode.
+
+ - Added the --delete-delay option, which is a more efficient way to
+ delete files at the end of the transfer without needing a separate
+ delete pass.
+
+ - You may specify --max-delete=0 to a 3.0.0 client as long as the
+ receiving side is at least version 3.0.0. This means that you
+ can pull from an older rsync with this option, but pushing to an
+ older rsync will generate an error. *Be sure to never specify a 0
+ value to an older rsync client, or it will be silently ignored.*
+
+ - The --hard-link option now uses less memory on both the sending and
+ receiving side for all protocol versions. For protocol 30, the use
+ of a hashtable on the sending side allows us to more efficiently
+ convey to the receiver what files are linked together. This reduces
+ the amount of data sent over the socket by a considerable margin
+ (rather than adding more data), and limits the in-memory storage of
+ the device+inode information to just the sending side for the new
+ protocol 30, or to the receiving side when speaking an older protocol
+ (note that older rsync versions kept the device+inode information on
+ both sides).