summaryrefslogtreecommitdiff
path: root/rdiff-backup/CHANGELOG
diff options
context:
space:
mode:
Diffstat (limited to 'rdiff-backup/CHANGELOG')
-rw-r--r--rdiff-backup/CHANGELOG52
1 files changed, 48 insertions, 4 deletions
diff --git a/rdiff-backup/CHANGELOG b/rdiff-backup/CHANGELOG
index fed3003..b431dca 100644
--- a/rdiff-backup/CHANGELOG
+++ b/rdiff-backup/CHANGELOG
@@ -1,16 +1,60 @@
New in v0.11.1 (2002/12/??)
---------------------------
+**Warning** Various features have been removed from this version, so
+this is not a safe upgrade. Also this version has less error
+checking, and, if it crashes, this version may be more prone to leave
+the destination directory in an inconsistent state. I plan to look at
+these issues in the next version. Also, this version is quite
+different from previous ones, so you cannot run version 0.11.1 on one
+end of a connection and any previous version on the other side.
+
+The following features have been removed:
+
+ --mirror-only option: If you just want to mirror something, use
+ rsync. (Or you could use rdiff-backup and then just delete the
+ rdiff-backup-data directory, and then update the root mtime.)
+
+ --change-source-perms option: This feature was pretty complicated
+ to implement, and if something happened to rdiff-backup during a
+ transfer, the old permissions could not be restored.
+
+ All "resume" related functionality, like --checkpoint-interval:
+ This was complicated to implement, and didn't seem to work all
+ that well.
+
+ Directory statistics file: Although the session statistics file is
+ still generated, the directory statistics file no longer is,
+ because the new code structure makes it less inconvenient.
+
+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
+module system.
+
+Now rdiff-backup writes metadata (uid, gid, mtime, etc.) to a
+compressed text file in the rdiff-backup-data directory. Here are
+some ramifications:
+
+ A user does not need root access on the destination side to record
+ file ownership information.
+
+ Some files may be recognized as not having changed based on this
+ metadata, so it may not be necessary to traverse the whole mirror
+ directory. This can reduce file access on the destination side.
+
+
+
+
+
Fixed bug with the --{include|exclude}-globbing-filelist options
(reported by Claus Herwig).
Added --list-changed-since option to list the files changed since the
-given date.
+given date, and added Bud Bruegger's patch to that. The format and
+information this option provides will probably change in the near
+future.
-Removed --mirror-only and --change-source-perms options.
-Removed all "resume" related functionality, like
---checkpoint-interval.
New in v0.11.0 (2002/10/05)