-NEWS for rsync version 2.5.8
-Protocol: 27 (changed)
-Changes since version 2.5.7:
-
- ENHANCEMENTS:
-
- * 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 verison
- 27. (J.W. Schultz)
-
- * Per-file dynamic block size is now sqrt(file length).
- The per-file checksum size is determined according
- to an algorythm 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.
+NEWS for rsync 2.6.7 (UNRELEASED)
+Protocol: 29 (unchanged)
+Changes since 2.6.6:
+
+ OUTPUT CHANGES:
+
+ - The letter 'D' in the itemized output was being used for both devices
+ (character or block) as well as other special files (such as fifos and
+ named sockets). This has changed to separate non-device special files
+ under the 'S' designation (e.g. "cS+++++++ path/fifo"). See also the
+ "--specials" option, below.
+
+ - 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-output (-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.