+NEWS for rsync 2.6.1 (UNRELEASED)
+Protocol: 27 (unchanged)
+Changes since 2.6.0:
+
+ ENHANCEMENTS:
+
+ * The RSYNC_PROXY environment variable can now contain a
+ "USER:PASS@" prefix before the "HOST:PORT" information.
+ (Bardur Arantsson)
+
+ * Lower memory use and more optimal transfer of file data.
+ (see the INTERNAL section).
+
+ BUG FIXES:
+
+ * The --link-dest code now works properly for a non-root user
+ when the UIDs of the source and destination differ and -u was
+ specified, and when the group of the source can't be used on
+ the destination and -g was specified. (Wayne Davison)
+
+ * Fixed a bug in the handling of -H (hard-links) that might
+ cause the expanded PATH/NAME value of the current item to
+ get overwritten (due to an expanded-name caching bug).
+ (Wayne Davison)
+
+ * Keep per-file track of the sending of literal data with
+ --partial so that an interrupted transfer doesn't keep a
+ shorter temp file when no new data has been transfered over
+ the wire.
+
+ * Fixed a byte-order problem in --batch-mode on big-endian
+ machines. (Jay Fenlason)
+
+ 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).
+
+ * More optimal data transmission for --hard-links (protocol 28).
+
+ * More optimal data transmission for --checksum (protocol 28).
+
+ * Less memory used for holding --checksum data.
+
+\f
NEWS for rsync 2.6.0 (1 Jan 2004)
Protocol: 27 (changed)
Changes since 2.5.7:
- 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 (i.e. /foo).
+ - "**/foo" now matches at the base of the transfer (like /foo
+ does). [Use "/**/foo" to get the old behavior in all versions.]
- - An non-anchored wildcard term floats to match beyond the base of
+ - 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.
+ 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).
+ "/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
regular file unless --delete specified. (J.W. Schultz)
* Detect and report when open or opendir succeed but read and
- readdir fail caused by network filesystems issues and truncated
+ readdir fail caused by network filesystem issues and truncated
files. (David Norwood, Michael Brown, J.W. Schultz)
* Added a fix that should give ssh time to restore the tty settings
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff