Renamed sum_table -> hash_table.

[rsync/rsync.git] / OLDNEWS

diff --git a/OLDNEWS b/OLDNEWS
index e811140..21f0735 100644 (file)
--- a/OLDNEWS
+++ b/OLDNEWS
@@ -17,11 +17,11 @@ Changes since 2.6.5:
       combined with --link-dest).
 
     - The outputting of hard-linked files when verbosity was > 1 was not right:
       combined with --link-dest).
 
     - The outputting of hard-linked files when verbosity was > 1 was not right:

-      without -i it would output the name of each hard-linked file as though
-      it had been changed (it now outputs a "is hard linked" message for the
-      file); with -i it would output all dots for the unchanged attributes of
-      a hard-link (it now changes those dots to spaces, as is done for other
-      totally unchanged items).
+      (1) Without -i it would output the name of each hard-linked file as
+      though it had been changed; it now outputs a "is hard linked" message for
+      the file. (2) With -i it would output all dots for the unchanged
+      attributes of a hard-link; it now changes those dots to spaces, as is
+      done for other totally unchanged items.

 
     - When backing up a changed symlink or device, get rid of any old backup
       item so that we don't get an "already exists" error.
 
     - When backing up a changed symlink or device, get rid of any old backup
       item so that we don't get an "already exists" error.


@@ -294,7 +294,7 @@ Changes since 2.6.3:
 
     - An OS that has a binary mode for its files (such as cygwin) needed
       setmode(fd, O_BINARY) called on the temp-file we opened with
 
     - An OS that has a binary mode for its files (such as cygwin) needed
       setmode(fd, O_BINARY) called on the temp-file we opened with

-      mkstemp().  (Fix derived from the cygwin's 2.6.3 rsync package.)
+      mkstemp().  (Fix derived from cygwin's 2.6.3 rsync package.)

 
     - Fixed a potential hang when verbosity is high, the client side is
       the sender, and the file-list is large.
 
     - Fixed a potential hang when verbosity is high, the client side is
       the sender, and the file-list is large.


@@ -359,9 +359,11 @@ Changes since 2.6.3:
       (since the forked process already has a copy of the exclude list,
       there's no need to send them a set of duplicates).
 
       (since the forked process already has a copy of the exclude list,
       there's no need to send them a set of duplicates).
 

-    - When --progress is specified, the output of items that the generator
-      is creating (e.g. dirs, symlinks) is now integrated into the progress
-      output without overlapping it.  (Requires protocol 29.)
+    - The output of the items that are being updated by the generator (dirs,
+      symlinks, devices) is now intermingled in the proper order with the
+      output from the items that the receiver is updating (regular files)
+      when pulling.  This misordering was particularly bad when --progress
+      was specified.  (Requires protocol 29.)

 
     - When --timeout is specified, lulls that occur in the transfer while
       the generator is doing work that does not generate socket traffic
 
     - When --timeout is specified, lulls that occur in the transfer while
       the generator is doing work that does not generate socket traffic


@@ -981,7 +983,7 @@ Changes since 2.6.0:
     - We now reset the "new data has been sent" flag at the start of
       each file we send.  This makes sure that an interrupted transfer
       with the --partial option set doesn't keep a shorter temp file
     - We now reset the "new data has been sent" flag at the start of
       each file we send.  This makes sure that an interrupted transfer
       with the --partial option set doesn't keep a shorter temp file

-      than the current basis file when no new data has been transfered
+      than the current basis file when no new data has been transferred

       over the wire for that file.
 
     - Fixed a byte-order problem in --batch-mode on big-endian machines.
       over the wire for that file.
 
     - Fixed a byte-order problem in --batch-mode on big-endian machines.


@@ -1685,6 +1687,8 @@ Changes since 2.4.6:
 \f
 Partial Protocol History
        RELEASE DATE    VER.    DATE OF COMMIT* PROTOCOL
 \f
 Partial Protocol History
        RELEASE DATE    VER.    DATE OF COMMIT* PROTOCOL

+       ?? ??? 2006     2.6.7                   29
+       28 Jul 2005     2.6.6                   29

        01 Jun 2005     2.6.5                   29
        30 Mar 2005     2.6.4   17 Jan 2005     29
        30 Sep 2004     2.6.3                   28
        01 Jun 2005     2.6.5                   29
        30 Mar 2005     2.6.4   17 Jan 2005     29
        30 Sep 2004     2.6.3                   28