+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.
+
+ BUG FIXES:
+
+ - Fixed a really old bug that caused --checksum (-c) to checksum all the
+ files encountered during the delete scan (ouch).
+
+ - Fixed a potential hang in a remote generator: when the receiver gets a
+ read-error on the socket, it now signals the generator about this so that
+ the generator does not try to send any of the terminating error messages
+ to the client (avoiding a potential hang in some setups).
+
+ - Made hard-links work with symlinks and devices again.
+
+ - If the sender gets an early EOF reading a source file, we propagate this
+ error to the receiver so that it can discard the file and try requesting
+ it again (which is the existing behavior for other kinds of read errors).
+
+ - If a device-file/special-file changes permissions, rsync now updates the
+ permissions without recreating the file.
+
+ - If the user specifies a remote-host for both the source and destination,
+ we now output a syntax error rather than trying to open the destination
+ hostspec as a filename.
+
+ - When --inplace creates a new destination file, rsync now creates it with
+ permissions 0600 instead of 0000 -- this makes restarting possible when
+ the transfer gets interrupted in the middle of sending a new file.
+
+ - Reject the combination of --inplace and --sparse since the sparse-output
+ algorithm doesn't work when overwriting existing data.
+
+ - Fixed the directory name in the error that is output when pop_dir()
+ fails.
+
+ - Really fixed the parsing of a "!" entry in .cvsignore files this time.
+
+ - If the generator gets a stat() error on a file, output it (this used to
+ require at least -vv for the error to be seen).
+
+ - If waitpid() fails or the child rsync didn't exit cleanly, we now handle
+ the exit status properly and generate a better error.
+
+ - Fixed some glitches in the double-verbose output when using --copy-dest,
+ --link-dest, or --compare-dest. Also improved how the verbose output
+ handles hard-links (within the transfer) that had an up-to-date alternate
+ "dest" file, and copied files (via --copy-dest).
+
+ - Fixed the matching of the dont-compress items (e.g. *.gz) against files
+ that have a path component containing a slash.
+
+ - If code reading a filter/exclude file an EINTR error, rsync now clears
+ the error flag on the file handle so it can keep on reading.
+
+ - If --relative is active, the sending side cleans up trailing "/" or "/."
+ suffixes to avoid triggering a bug in older rsync versions. Also, we now
+ reject a ".." dir if it would be sent as a relative dir.
+
+ - If a non-directory is in the way of a directory and rsync is run with
+ --dry-run and --delete, rsync no longer complains about not being able
+ to opendir() the not-yet present directory.
+
+ - When --list-only is used and a non-existent local destination dir was
+ also specified as a destination, rsync no longer generates a warning
+ about being unable to create the missing directory.
+
+ - Fixed some problems with --relative --no-implied-dirs when the
+ destination directory did not yet exist: we can now create a symlink or
+ device when it is the first thing in the missing dir, and --fuzzy no
+ longer complains about being unable to open the missing dir.
+
+ - Fixed a bug where the --copy-links option would not affect implied
+ directories without --copy-unsafe-links (see --relative).
+
+ - Got rid of the need for --force to be used in some circumstances with
+ --delete-after (making it consistent with --delete-before/-during).
+
+ - Rsync now ignores the SIGXFSZ signal, just in case your OS sends this
+ when a file is too large (rsync handles the write error).
+
+ - Fixed a bug in the Proxy-Authorization header's base64-encoded value: it
+ was not properly padded with trailing '=' chars. This only affects a
+ user that need to use a password-authenticated proxy for an outgoing
+ daemon-rsync connection.
+
+ - Fixed a bug in the debug output (-vvvvv) that could mention the wrong
+ checksum for the current file offset.
+
+ - Rsync no longer allows a single directory to be copied over a non-
+ directory destination arg.