- INTERNAL:
-
- * Most of the I/O is now buffered, which results in a pretty
- large speedup when running under MS Windows. (Craig Barratt)
-
- * Optimizations to the name-handling/comparing code have made
- some significant reductions in user-CPU time for large file
- sets. (Wayne Davison)
-
- * Some variable-type cleanup that makes the code more consistent.
- (Wayne Davison)
-
- * Reduced memory requirements of hard link preservation.
- (J.W. Schultz)
-
- * Got rid of support for protocol versions 17 and 18 (which are
- both over 6 years old). (Wayne Davison)
-
- * More optimal data transmission for --hard-links (protocol 28).
-
- * More optimal data transmission for --checksum (protocol 28).
-
- * Less memory used for holding --checksum data.
-
- * Less memory used per-file in the file list.
-
-\f
-NEWS for rsync 2.6.0 (1 Jan 2004)
-Protocol: 27 (changed)
-Changes since 2.5.7:
-
- ENHANCEMENTS:
-
- * "ssh" is now the default remote shell for rsync. If you want to
- change this, configure like this: "./configure --with-rsh=rsh".
-
- * Added --files-from, --no-relative, --no-implied-dirs, and --from0.
- Note that --from0 affects the line-ending character for all the
- files read by the --*-from options. (Wayne Davison)
-
- * Length of csum2 is now per-file starting with protocol version
- 27. (J.W. Schultz)
-
- * Per-file dynamic block size is now sqrt(file length). The
- per-file checksum size is determined according to an algorithm
- provided by Donovan Baarda which reduces the probability of rsync
- algorithm corrupting data and falling back using the whole md4
- checksums. (J.W. Schultz, Donovan Baarda)
-
- * The --stats option no longer includes the (debug) malloc summary
- unless the verbose option was specified at least twice.
-
- * Added a new error/warning code for when files vanish from the
- sending side. Made vanished source files not interfere with the
- file-deletion pass when --delete-after was specified.
-
- * Various trailing-info sections are now preceded by a newline.
-
- 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.]