X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/0f7e31f7d71e55e5d3bc809e58dbc045a72c4baf..e4b808989ee9927654b13e03e26f74e5703c405d:/NEWS

diff --git a/NEWS b/NEWS
index dc7a6a71..3f76c0b5 100644
--- a/NEWS
+++ b/NEWS
@@ -148,8 +148,9 @@ Changes since 2.6.3:
       filter files (like .cvsignore, but with full filter-rule parsing).
       This new option was chosen in order to ensure that all existing
       include/exclude processing remained 100% compatible with older
-      versions.  (Protocol 29 needed for full filter-rule support, but
-      backward-compatible rules work with earlier protocol versions.)
+      versions.  Protocol 29 is needed for full filter-rule support, but
+      backward-compatible rules work with earlier protocol versions.
+      (Promoted from the patches dir.)
 
     - Added the --delay-updates option that puts all updated files into
       a temporary directory (by default ".~tmp~", but settable via the
@@ -166,6 +167,20 @@ Changes since 2.6.3:
       they are given, and refuse to operate on a directory index (since
       that would indicate that something had gone very wrong).
 
+    - Added the --itemize-changes (-i) option that is a way to output the
+      list of files that got transferred and/or changed in any way, and how
+      they changed.  The effect is the same as specifying --log-format
+      "%i %n%L" (see the rsyncd.conf manpage).  Works with --dry-run.
+
+    - Added the --fuzzy option, which attempts to find a basis file for a
+      file that is being created from scratch.  The current algorithm
+      only looks in the destination directory for the created file, but
+      it does attempt to find a match based on size/mod-time (in case the
+      file was renamed with no other changes) as well as based on a fuzzy
+      name-matching algorithm.  This option requires protocol 29 because
+      it needs the new file-sorting order.  (Promoted from patches dir
+      and enhanced.)
+
   SUPPORT FILES:
 
     - Added support/atomic-rsync -- a perl script that will transfer some
@@ -207,6 +222,10 @@ Changes since 2.6.3:
     - Defined int32 in a way that ensures that the build dies if we can't
       find a variable with at least 32 bits.
 
+    - The daemon's "read only" config item now sets an internal read_only
+      variable that makes extra sure that no write/delete calls on the
+      read-only side can succeed.
+
   PROTOCOL DIFFERENCES FOR VERSION 29:
 
     - If --inplace is specified, the generator sends an extra byte after
@@ -220,10 +239,11 @@ Changes since 2.6.3:
       filter rules so it is positioned correctly (unlike in some older
       transfer scenarios).
 
-    - Rsync sorts the filename list in a slightly different way for some
-      rare sets of files:  it always puts a dir's contents immediately
-      after the dir in the list.  (Previously an item named "foo.txt" would
-      sort in between directory "foo" and "foo/bar".)
+    - Rsync sorts the filename list in a different way:  it sorts the
+      subdir names after the non-subdir names for each dir's contents, and
+      it always puts a dir's contents immediately after the dir's name in
+      the list.  (Previously an item named "foo.txt" would sort in between
+      directory "foo/" and "foo/bar".)
 
     - When talking to a protocol 29 rsync daemon, a list-only request
       is able to note this before the options are sent over the wire, and
@@ -234,6 +254,13 @@ Changes since 2.6.3:
       build the file-list, and one for how long it took to send it over the
       wire (each expressed in thousandths of a second).
 
+    - When --delete-excluded is specified with some filter rules (AKA
+      excludes), a client sender will still initiate a send of the filter
+      rules to the receiver, but it only includes those rules that are
+      receiver-specific.  Older protocols used to omit the sending of
+      excludes in this situation (since there were no receiver-specific
+      rules that survived --delete-excluded back then).
+
     - A protocol-29 batch file includes a bit for the setting of the --dirs
       option.  Also, the shell script created by --write-batch will use the
       --filter option instead of --exclude-from to capture any filter rules.