filter rules so it is positioned correctly (unlike in some older
transfer scenarios).
- - Rsync sorts the filename list in a slightly different way for some
- rare sets of files: it always puts a dir's contents immediately
- after the dir in the list. (Previously an item named "foo.txt" would
- sort in between directory "foo" and "foo/bar".)
+ - Rsync sorts the filename list in a different way: it sorts the
+ subdir names after the non-subdir names for each dir's contents, and
+ it always puts a dir's contents immediately after the dir's name in
+ the list. (Previously an item named "foo.txt" would sort in between
+ directory "foo/" and "foo/bar".)
- When talking to a protocol 29 rsync daemon, a list-only request
is able to note this before the options are sent over the wire, and
build the file-list, and one for how long it took to send it over the
wire (each expressed in thousandths of a second).
+ - When --delete-excluded is specified with some filter rules (AKA
+ excludes), a client sender will still initiate a send of the filter
+ rules to the receiver, but it only includes those rules that are
+ receiver-specific. Older protocols used to omit the sending of
+ excludes in this situation (since there were no receiver-specific
+ rules that survived --delete-excluded back then).
+
- A protocol-29 batch file includes a bit for the setting of the --dirs
option. Also, the shell script created by --write-batch will use the
--filter option instead of --exclude-from to capture any filter rules.
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff