X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/40f910c43ae4f3afdfc8edbe40ca695ecd786b57..b06050f9ad6657a41b5ca5f7e205e48ed6edb173:/NEWS

diff --git a/NEWS b/NEWS
index 38655bf1..bfc2d836 100644
--- a/NEWS
+++ b/NEWS
@@ -41,9 +41,6 @@ Changes since 2.6.8:
     - If the receiving side fails to create a directory, it will now skip
       trying to update everything that is inside that directory.
 
-    - Make sure that the --link-dest option can still do its job even when -I
-      is specified.
-
     - If --link-dest is specified with --checksum but without --times, rsync
       will now allow a hard-link to be created to a matching link-dest file
       even when the file's modify-time doesn't match the server's file.
@@ -68,6 +65,17 @@ Changes since 2.6.8:
     - Fixed a recent bug where an --exclude='*' could affect the root (/) of
       the filesystem with --relative enabled.
 
+    - When --inplace creates a file, it is now created with owner read/write
+      permissions (0600) instead of no permissions at all.  This avoids a
+      problem continuing a transfer that was interrupted (since --inplace
+      will not update a file that has no write permissions).
+
+    - If either --remove-source-files or --remove-sent-files is enabled and we
+      are unable to remove the source file, rsync now outputs an error.
+
+    - Fixed a bug in the daemon's "incoming chmod" rule: newly-created
+      directories no longer get the 'F' (file) rules applied to them.
+
   ENHANCEMENTS:
 
     - Added the --log-file=FILE and --log-file-format=FORMAT options.  These
@@ -87,6 +95,15 @@ Changes since 2.6.8:
       tweaking of "unsafe" symlinks, but it can now be consistently applied
       regardless of how "use chroot" is set.
 
+    - Added the --remove-source-files option as a replacement for the (now
+      deprecated) --remove-sent-files option.  This new option removes all
+      non-dirs from the source directories, even if the file was already
+      up-to-date.  This fixes a problem where interrupting an rsync that
+      was using --remove-sent-files and restarting it could leave behind
+      a file that the earlier rsync synchronized, but didn't get to remove.
+      (The deprecated --remove-sent-files is still understood for now, and
+      still behaves in the same way as before.)
+
     - Added a new environment variable to the pre-/post-xfer exec commands (in
       the daemon's config file):  RSYNC_PID.  This value will be the same in
       both the pre- and post-xfer commands, so it can be used if the pre-xfer