X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/889ae39d7adc30ecfdacc39b37c8d9c11cdabb7f..ab3d6c6025162c19c082602aa1e488f22e40d392:/NEWS

diff --git a/NEWS b/NEWS
index 6ee4601f..3d51c537 100644
--- a/NEWS
+++ b/NEWS
@@ -25,8 +25,22 @@ Changes since 2.6.9:
       files (which includes local copies).  Version 2.6.9 would complete the
       copy, but exit with an error when the receiver output its memory stats.
 
+    - If --password-file is used on a non-daemon transfer, rsync now complains
+      and exits.  This should help users figure out that they can't use this
+      option to control a remote shell's password prompt.
+
   ENHANCEMENTS:
 
+    - A new incremental-recursion algorithm is now used when rsync is talking
+      to another 3.0.0 version.  This starts the transfer going more quickly
+      (before all the files have been found), and requires much less memory.
+      See the --recursive option in the manpage for some restrictions.
+
+    - The default --delete algorithm is now --delete-during when talking to a
+      3.x rsync.  This is a faster scan than using --delete-before (which is
+      the default when talking to older rsync versions), and is compatible
+      with the new incremental recursion mode.
+
     - Added the --delete-delay option, which is a more efficient way to
       delete files at the end of the transfer without needing a separate
       delete pass.
@@ -41,11 +55,12 @@ Changes since 2.6.9:
       receiving side for all protocol versions.  For protocol 30, the use
       of a hashtable on the sending side allows us to more efficiently
       convey to the receiver what files are linked together.  This reduces
-      the amount of data sent over the socket by a considerable margin, and
-      moves the in-memory storage of the device+inode information from the
-      receiving side (for protocols < 30) to the sending side (note that
-      older rsync versions kept the device+inode information on both
-      sides).
+      the amount of data sent over the socket by a considerable margin
+      (rather than adding more data), and limits the in-memory storage of
+      the device+inode information to just the sending side for the new
+      protocol 30, or to the receiving side when speaking an older protocol
+      (note that older rsync versions kept the device+inode information on
+      both sides).
 
   INTERNAL: