For incrementals, we *must* read dumpdates (fail if it's not there!).

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 7f99d5fb5c2f04916e23321b2bd19fc2eab94509..607a400f78831b73bdc42db0d60effcdf8d6b9fe 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.9 1999/10/30 22:55:45 tiniou Exp $
+$Id: CHANGES,v 1.10 1999/10/31 19:48:25 tiniou Exp $

 
 Changes between versions 0.4b7 and 0.4b8 (released ???????????????)
 ===================================================================
 
 Changes between versions 0.4b7 and 0.4b8 (released ???????????????)
 ===================================================================


@@ -22,6 +22,11 @@ Changes between versions 0.4b7 and 0.4b8 (released ???????????????)
        bypass the security limitations of rcmd). Now you can do remote
        backups without being root (or making dump setuid root).
 
        bypass the security limitations of rcmd). Now you can do remote
        backups without being root (or making dump setuid root).
 

+6.     Modified again the way dumpdates works. For incremental dumps,
+       we need to read dumpdates even if we are not using 'u' option.
+       Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
+       this should work.
+

 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
 ===================================================================
 
 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
 ===================================================================