X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/c7b1a56b3d70fb91b20702f169ae1af9b68de8e9..bb6721dce6bac8ff2374609bf5f99ea7e6fe2c70:/NEWS

diff --git a/NEWS b/NEWS
index 4cffa09a..58afa336 100644
--- a/NEWS
+++ b/NEWS
@@ -2,6 +2,18 @@ NEWS for rsync 2.6.3 (UNRELEASED)
 Protocol: 28 (unchanged)
 Changes since 2.6.2:
 
+  OUTPUT CHANGES:
+
+    - For anyone who is parsing rsync's verbose output using a script,
+      please note that the 2-line footer now uses the term "sent" instead
+      of "wrote" and "received" instead of "read".  If you are not parsing
+      the numeric values out of this footer, your script would probably be
+      better off using the empty line prior to the footer as the indicator
+      that the verbose output is over.
+      
+    - The --stats option was similarly affected to change "written" to
+      "sent" and "read" to "received".
+
   BUG FIXES:
 
     - Fixed a crash bug that might appear when --delete was used and
@@ -17,11 +29,14 @@ Changes since 2.6.2:
       the password file (by the client):  the files no longer need to be
       terminated by a newline for their content to be read in.
 
-    - If a file has a read error on the sending side, the receiver will
-      no longer keep the resulting file unless the --partial option was
-      specified.  (Note:  both sides must be running 2.6.3 for this to
-      work -- older receivers always keep the file, and older senders
-      don't tell the receiver that the file was not read correctly.)
+    - If a file has a read error on the sending side or the reconstructed
+      data doesn't match the expected checksum (perhaps due to the basis
+      file changing during the transfer), the receiver will no longer
+      retain the resulting file unless the --partial option was specified.
+      (Note: for the read-error detection to work, neither side can be
+      older than 2.6.3 -- older receivers will always retain the file, and
+      older senders don't tell the receiver that the file had a read
+      error.)
 
     - If a file gets resent in a single transfer and the --backup option
       is enabled, rsync no longer performs a duplicate backup (losing the
@@ -63,12 +78,34 @@ Changes since 2.6.2:
       suggest that the user specify --ipv4 or --ipv6 (if we think it will
       help).
 
+    - When the remote rsync dies, make a better effort to recover any error
+      messages it may have sent instead of just dying with a write error
+      trying to send data over the socket.
+
+    - When using --delete and a --backup-dir that contains files that are
+      hard-linked to their destination equivalents, rsync now makes sure
+      that removed files really get removed (works around a really weird
+      rename() behavior).
+
+    - Avoid a bogus run-time complaint about a lack of 64-bit integers when
+      the int64 type is defined as an off_t and it actually has 64-bits.
+
   ENHANCEMENTS:
 
+    - Added the --partial-dir=DIR option that lets you specify where to
+      (temporarily) put a partially transferred file (instead of over-
+      writing the destination file).  E.g.  --partial-dir=.rsync-partial
+
     - Added --keep-dirlinks (-K), which allows you to symlink a directory
       onto another partition on the receiving side and have rsync treat it
       as matching a normal directory from the sender.
 
+    - Added the --inplace option that tells rsync to write each destination
+      file without using a temporary file.  The matching of existing data
+      in the destination file can be severely limited by this, but there
+      are also cases where this is more efficient (such as appending data).
+      Use only when needed (see the man page for more details).
+
     - Added the "write only" option to the daemon's config file.
 
     - Added long-option names for -4 and -6 (namely --ipv4 and --ipv6)
@@ -83,6 +120,22 @@ Changes since 2.6.2:
 
     - Added the --checksum-seed=N option for advanced users.
 
+    - Batch writing/reading has a brand-new implementation that is simpler,
+      fixes a few weird problems with the old code (such as no longer
+      sprinkling the batch files into different dirs or even onto different
+      systems), and is much less intrusive into the code (making it easier
+      to maintain for the future).  The new code generates just one data
+      file instead of three, which makes it possible to read the batch via
+      stdin.  Also, the old requirement of using the same fixed checksum-
+      seed for all batch processing has been removed.
+
+    - If an rsync daemon has a module set with "list = no" (which hides its
+      presence in the list of available modules), a user that fails to
+      authenticate gets the same "unknown module" error that they would get
+      if the module were actually unknown (while still logging the real
+      error to the daemon's log file).  This prevents fishing for modules
+      names.
+
   INTERNAL:
 
     - Some cleanup in the exclude code has saved some per-exclude memory
@@ -99,8 +152,15 @@ Changes since 2.6.2:
       handles after we accept a connection (we used to close just one of
       them).
 
+    - Optimized the handling of larger block sizes (rsync used to slow to
+      a crawl if the block size got too large).  Also cap the block size.
+
     - Optimized away a loop in hash_search().
 
+    - Make sure that a filename that contains a newline gets mentioned with
+      each newline transformed into a question mark (which makes parsing
+      the verbose output via script more dependable).
+
   BUILD CHANGES:
 
     - Added a "gen" target to rebuild most of the generated files,