-NEWS for rsync 2.6.1 (UNRELEASED)
-Protocol: 27 (unchanged)
-Changes since 2.6.0:
-
- ENHANCEMENTS:
-
- * Lower memory use and more optimal transfer of data over
- the socket (see the INTERNAL section for details).
-
- * The RSYNC_PROXY environment variable can now contain a
- "USER:PASS@" prefix before the "HOST:PORT" information.
- (Bardur Arantsson)
-
- * The --progress output now mentions how far along in the
- transfer we are, including both a count of files transferred
- and a percentage of the total file-count that we're processed.
-
- * The configure script now accepts --with-rsyncd-conf=PATH
- to override the default value of the /etc/rsyncd.conf file.
+NEWS for rsync 2.6.7 (UNRELEASED)
+Protocol: 29 (unchanged)
+Changes since 2.6.6:
+
+ OUTPUT CHANGES:
+
+ - The itemized output now uses 'S' for a special file instead of
+ clumping them together with the 'D' for devices. The number of
+ characters is also different (to remove an unused field).
+
+ - The way rsync escapes unreadable characters has changed. First, rsync
+ now has support for recognizing valid multibyte character sequences in
+ your current locale, allowing it to escape fewer characters than before
+ for a locale such as UTF-8. Second, it now uses an escape idiom of
+ "\#123", which is the literal string "\#" followed by exactly 3 octal
+ digits. Rsync no longer doubles a backslash character in a filename
+ (e.g. it used to output "foo\\bar" when copying "foo\bar") -- now it only
+ escapes a backslash that is followed by a hash-sign and 3 digits (0-9)
+ (e.g. it will output "foo\#134#789" when copying "foo\#789"). See also
+ the --8-bit (-8) option, mentioned below.
+
+ Script writers: the local rsync is the one that outputs escaped names,
+ so if you need to support unescaping of filenames for older rsyncs, I'd
+ suggest that you parse the output of "rsync --version" and only use the
+ old unescaping rules for 2.6.5 and 2.6.6.