- BUG FIXES:
-
- * Fixed several exclude/include matching bugs when using wild-cards.
- This has a several user-visible effects, all of which make the
- matching more consistent and intuitive. This should hopefully not
- cause anyone problems since it makes the matching work more like
- what people are expecting. (Wayne Davison)
-
- - A pattern with a "**" no longer causes a "*" to match slashes.
- For example, with "/*/foo/**", "foo" must be 2 levels deep.
- [If your string has BOTH "*" and "**" wildcards, changing the
- "*" wildcards to "**" will provide the old behavior in all
- versions.]
-
- - "**/foo" now matches at the base of the transfer (like /foo
- does). [Use "/**/foo" to get the old behavior in all versions.]
-
- - A non-anchored wildcard term floats to match beyond the base of
- the transfer. E.g. "CVS/R*" matches at the end of the path,
- just like the non-wildcard term "CVS/Root" does. [Use "/CVS/R*"
- to get the old behavior in all versions.]
-
- - Including a "**" in the match term causes it to be matched
- against the entire path, not just the name portion, even if
- there aren't any interior slashes in the term. E.g. "foo**bar"
- would exclude "/path/foo-bar" (just like before) as well as
- "/foo-path/baz-bar" (unlike before). [Use "foo*bar" to get the
- old behavior in all versions.]
-
- * The exclude list specified in the daemon's config file is now
- properly applied to the pulled items no matter how deep the
- user's file-args are in the source tree. (Wayne Davison)
-
- * For protocol version >= 27, mdfour_tail() is called when the
- block size (including checksum_seed) is a multiple of 64.
- Previously it was not called, giving the wrong MD4 checksum.
- (Craig Barratt)
-
- * For protocol version >= 27, a 64 bit bit counter is used in
- mdfour.c as required by the RFC. Previously only a 32 bit bit
- counter was used, causing incorrect MD4 file checksums for
- file sizes >= 512MB - 4. (Craig Barratt)
+ - 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).