Eliminate unexistent prototype gcc warning.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 897451281f5f82b7284472a2d1ac9a4b52d2db61..2997fcb8406185b623d39954ea38784a3bf0f5e6 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.193 2002/08/18 20:52:04 stelian Exp $
+$Id: CHANGES,v 1.198 2002/11/15 09:49:39 stelian Exp $
 
 Changes between versions 0.4b31 and 0.4b32 (released ?????????????)
 ===================================================================
@@ -17,6 +17,29 @@ Changes between versions 0.4b31 and 0.4b32 (released ?????????????)
        <jorgen_ostling@users.sourceforge.net> for reporting this 
        bug.
 
+3.     Fixed dump's estimate when dealing with sparse inodes.
+
+4.     Modified dump to allow setting a blocksize bigger than 32kB
+       (raised the limit to 1024kB), because newer hardware needs
+       this for proper operation. Thanks to Dirk Traenapp
+       <dtraenapp@users.sourceforge.net> for reporting this.
+
+5.     Fixed a bug causing Dump to stop and report an error if an
+       inode number in the exclude file was followed by some amount
+       of whitespace. Thanks to Jeffrey Sofferin 
+       <sofferin@users.sourceforge.net> for reporting this bug.
+
+6.     Fixed a bug which caused restore, in some particular cases,
+       to ask some 'scary' questions and leave a bunch of RSTTMP
+       directories behind when restoring incremental tapes. Thanks
+       to Philippe Troin <phil@fifi.org> for reporting this bug and
+       providing the test cases.
+
+7.     Changed the wording when inodes are excluded from dump:
+       replaced 'Added inode 7 to exclude list' with
+       'Excluding inode 7 (resize inode) from dump', as suggested
+       by Elliott Mitchell <ehem@m5p.com> in a Debian bug report.
+
 Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002)
 ===================================================================