summaryrefslogtreecommitdiff
path: root/rdiff-backup/CHANGELOG
diff options
context:
space:
mode:
Diffstat (limited to 'rdiff-backup/CHANGELOG')
-rw-r--r--rdiff-backup/CHANGELOG22
1 files changed, 17 insertions, 5 deletions
diff --git a/rdiff-backup/CHANGELOG b/rdiff-backup/CHANGELOG
index b431dca..5bd54b3 100644
--- a/rdiff-backup/CHANGELOG
+++ b/rdiff-backup/CHANGELOG
@@ -1,4 +1,4 @@
-New in v0.11.1 (2002/12/??)
+New in v0.11.1 (2002/12/31)
---------------------------
**Warning** Various features have been removed from this version, so
@@ -27,8 +27,15 @@ The following features have been removed:
still generated, the directory statistics file no longer is,
because the new code structure makes it less inconvenient.
+ The various --exclude and --include options no longer work when
+ restoring. This may be added later if there is demand.
+
+ --windows-mode and filename quoting doesn't work. There have been
+ several requests for this in the past, so it will probably be
+ re-added in the next version.
+
Extensive refactoring. A lot of rdiff-backup's code was structured as
-if it was still in one file, so it didn't make enough use of Python's
+if it were still in one file, so it didn't make enough use of Python's
module system.
Now rdiff-backup writes metadata (uid, gid, mtime, etc.) to a
@@ -42,9 +49,13 @@ some ramifications:
metadata, so it may not be necessary to traverse the whole mirror
directory. This can reduce file access on the destination side.
+ Even when the --no-hard-links option is given when backing up,
+ link relationships can be restored properly. However, if this
+ option is given, mirror files will not be linked together.
-
-
+ Special file types like device and sockets which cannot be created
+ on the remote side for some reason can still be backed up and
+ restored properly.
Fixed bug with the --{include|exclude}-globbing-filelist options
(reported by Claus Herwig).
@@ -54,7 +65,8 @@ given date, and added Bud Bruegger's patch to that. The format and
information this option provides will probably change in the near
future.
-
+Restoring is now pipelined for better high latency performance, and
+unchanged files in the target directory will not be recopied.
New in v0.11.0 (2002/10/05)