Fix another hashtree bug in restore causing "removenode: non-empty directory"

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 91f827e549898f08815b21bceadf5e7e5915701b..d6d93ff0bea45300ee43b4ead586f709d757eaaa 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,31 @@
-$Id: CHANGES,v 1.268 2005/01/14 13:04:56 stelian Exp $
+$Id: CHANGES,v 1.273 2005/03/18 22:12:54 stelian Exp $
 
-Changes between versions 0.4b38 and 0.4b39 (released ???????????????)
-=====================================================================
+Changes between versions 0.4b39 and 0.4b40 (released ????????????????)
+======================================================================
+
+1.     Changed restore to emit warnings (instead of emitting a fatal
+       error) if a file (or a directory) is unavailable for a 
+       comparision (if the user doesn't have the necessary permissions
+       to access it for example). Thanks to Kenneth Porter
+       <shiva@sewingwitch.com> for the bug report.
+
+2.     Re-done the 'do not save directory entries to non-dumped inodes
+       (excluded from dump)' feature. The previous implementation
+       worked well for excluded directories but not for regular files.
+       Thanks to Kenneth Porter <shiva@sewingwitch.com> for the bug
+       report.
+
+3.     Fixed a bug in dump where the tape size was miscalculated when
+       the user used -d/-s to specify the tape characteristics. Thanks
+       to Philip Goisman <goisman@physics.arizona.edu> for reporting
+       the bug.
+
+4.     Fixed another bug introduced in restore with the hashtree
+       implementation. This one caused restore to stop saying
+       "removenode: non-empty directory" in some cases.
+
+Changes between versions 0.4b38 and 0.4b39 (released January 21, 2005)
+======================================================================
 
 1.     The newly added dump_on_cd_3 example was buggy, replace it
        with an updated version from Andrew Basterfield