+rsync 2.5.5 "Snowy River" (2 April 2002)
+protocol: 26 (unchanged)
+
+ ENHANCEMENTS:
+
+ * With --progress, when a transfer is complete show the time taken;
+ otherwise show expected time to complete. (Cameron Simpson)
+
+ * Make "make install-strip" works properly, and "make install"
+ accepts a DESTDIR variable for help in building binary packages.
+ (Peter Breitenlohner, Greg Louis)
+
+ * If configured with --enable-maintainer-mode, then on receipt of
+ a fatal signal rsync will try to open an xterm running gdb,
+ similarly to Samba's "panic action" or GNOME's bug-buddy.
+ (Martin Pool)
+
+
+ BUG FIXES:
+
+ * Fix situation where failure to fork (e.g. because out of process
+ slots) would cause rsync to kill all processes owned by the
+ current user. Yes, really! (Paul Haas, Martin Pool)
+
+ * Fix test suite on Solaris. (Jos Backus, Martin Pool)
+
+ * Fix minor memory leak in socket code. (Dave Dykstra, Martin
+ Pool.)
+
+ * Fix --whole-file problem that caused it to be the default even
+ for remote connections. (Martin Pool, Frank Schulz)
+
+ * Work around bug in Mac OS X mkdir(2), which cannot handle
+ trailing slashes.
+ <http://www.opensource.apple.com/bugs/X/BSD%20Kernel/2734739.html>
+ (Martin Pool)
+
+ * Improved network error handling. (Greg A. Woods)
+
+\f
+rsync 2.5.4 (13 March 2002)
+protocol: 26 (unchanged)
+
+ "Imitation lizard skin"
+
+ BUG FIXES:
+
+ * Additional fix for zlib double-free bug. (Martin Pool, Andrew
+ Tridgell) (CVE CAN-2002-0059)
+
+ ENHANCEMENTS:
+
+ * Merge in changes from zlib 1.1.3 to zlib 1.1.4. (Jos Backus)
+ (Note that rsync still uses a custom version of zlib; you can
+ not just link against a system library. See zlib/README.rsync)
+
+ * Additional test cases for --compress. (Martin Pool)
+
+\f
+rsync 2.5.3 (11 March 2002)
+protocol: 26 (unchanged)
+
+ "Happy 26"
+
+ SECURITY FIXES:
+
+ * Make sure that supplementary groups are removed from a server
+ process after changing uid and gid. (Ethan Benson) (Debian bug
+ #132272, CVE CAN-2002-0080)
+
+ BUG FIXES:
+
+ * Fix zlib double-free bug. (Owen Taylor, Mark J Cox) (CVE
+ CAN-2002-0059)
+
+ * Fixed problem that in many cases caused the error message
+ unexpected read size of 0 in map_ptr
+ and resulted in the wrong data being copied.
+
+ * Fixed compilation errors on some systems caused by the use of
+ "unsigned int64" in rsync.h.
+
+ * Fixed problem on systems such as Sunos4 that do not support realloc
+ on a NULL pointer; error was "out of memory in flist_expand".
+
+ * Fix for rsync server processes hanging around after the client
+ unexpectedly disconnects. (Colin Walters) (Debian bug #128632)
+
+ * Cope with BSD systems on which mkdir() will not accept a trailing
+ slash.
+
+ ENHANCEMENTS:
+
+ * Merge in changes from zlib 1.1.2 to zlib 1.1.3. (Note that
+ rsync still uses a custom version of zlib; you can not just link
+ against a system library. See zlib/README.rsync)
+
+ * Command to initiate connections is only shown with -vv, rather
+ than -v as in 2.5.2. Output from plain -v is more similar to
+ what was historically used so as not to break scripts that try
+ to parse the output.
+
+ * Added --no-whole-file and --no-blocking-io options (Dave Dykstra)
+
+ * Made the --write-batch and --read-batch options actually work
+ and added documentation in the man page (Jos Backus)
+
+ * If the daemon is unable to fork a child to accept a connection,
+ print an error message. (Colin Walters)
+
rsync 2.5.2 (26 Jan 2002)
+protocol: 26 (changed)
SECURITY FIXES:
Vipul's Razor. (Debian #124286)
rsync 2.5.1 (2002-01-03)
+protocol: 25 (unchanged)
BUG FIXES:
* Clearer error messages for some conditions.
+\f
rsync 2.5.0 (2001-11-30)
+protocol: 25 (changed)
ANNOUNCEMENTS
* The existing test.sh script by Phil Hands has been merged into a
test framework that works from both "make check" and the Samba
build farm.
+\f
+Partial Protocol History
+ DATE RELEASE PROTOCOL
+ 2003/01/26 20:11:16 release-2-5-6 26
+ 2002/02/23 00:17:50 release-2-5-3 26
+ 2002/01/25 23:00:21 release-2-5-2 26
+ 2001/12/18 06:47:40 release-2-5-1 25
+ release-2-4-6 24
+ 2000/08/16 08:34:18 release-2-4-5 24
+ 2000/07/29 04:52:05 release-2-4-4 24
+ 2000/03/30 14:15:00 release-2-4-2 24
+ 2000/01/29 23:49:36 release-2-4-1 24
+ 2000/01/29 02:56:37 release-2-4-0 23
+ release-2-3-3 21
+ 1999/06/26 01:06:38 release-2-3-2 21
+ release-2-3-1 20
+ 1999/03/15 21:17:59 release-2-3-0 20
+ 1998/11/15 01:21:42 release-2-2-1 19
+ 1998/11/03 07:08:28 release-2-2-0 19
+ 1998/09/09 06:31:14 release-2-1-1 19
+ 1998/07/17 14:43:05 release-2-0-19 19
+ 1998/06/18 12:17:24 release-2-0-18 19
+ 1998/06/18 09:51:56 release-2-0-17 19
+ 1998/06/01 03:42:22 release-2-0-16 19
+ 1998/05/27 13:47:34 release-2-0-13 19
+ 1998/05/26 14:19:00 release-2-0-12 18
+ 1998/05/21 05:55:33 release-2-0-11 18
+ 1998/05/18 08:20:34 release-2-0-9 18
+ 1998/05/17 05:56:33 release-2-0-8 17
+ 1998/05/15 07:34:21 release-2-0-2 17
+ 1998/05/13 15:44:11 release-2-0-0 17
+ 1998/04/17 06:07:26 release-1-7-4 17
+ 1998/04/05 06:43:55 release-1-7-2 17
+ 1998/03/26 04:18:57 release-1-7-0 17 MAX=30
+ 1998/01/13 15:57:32 release-1-6-9 15 MAX=20
+ 1997/12/17 11:07:30 release-1-6-7 14
+ 1997/12/15 18:36:21 release-1-6-4 14
+
+* DATE OF COMMIT is the date the protocl change was committed
+ to cvs, not the release date.