'Set permission on the current directory ?' explanation.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index e6dd0f75b1165d97e9f0b802c151fa2c858e48f4..b6a75f828a7be71448b226ac7f641cffcce702a5 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,14 @@
-$Id: CHANGES,v 1.196 2002/10/07 19:27:35 stelian Exp $
+$Id: CHANGES,v 1.200 2002/11/19 13:39:35 stelian Exp $
 
-Changes between versions 0.4b31 and 0.4b32 (released ?????????????)
-===================================================================
+Changes between versions 0.4b32 and 0.4b33 (released ?????????????????)
+=======================================================================
+
+1.     Added a note in the restore man page clarifying the question
+       'set the permissions on the current directory ?' asked by
+       restore at the end of treatment in -i and -x modes.
+
+Changes between versions 0.4b31 and 0.4b32 (released November 15, 2002)
+=======================================================================
 
 1.     Changed dump to use fcntl(F_SETLK) style locking instead
        of flock() when locking the dumpdates file. With the old 
@@ -29,6 +36,17 @@ Changes between versions 0.4b31 and 0.4b32 (released ?????????????)
        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)
 ===================================================================