TODO cleanups

git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@370 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109

1 files changed, 12 insertions, 12 deletions

diff --git a/rdiff-backup/TODO b/rdiff-backup/TODO
index a203a16..8a8c3c8 100644
--- a/rdiff-backup/TODO
+++ b/rdiff-backup/TODO
@@ -1,10 +1,21 @@
+Fix for Python 2.3
+
+Change for librsync 0.9.6 when it comes out
+
 Use ctime to check whether files have been changed.  See message:
 http://mail.gnu.org/archive/html/rdiff-backup-users/2003-06/msg00050.html
 by Andrew Bressen.
 
 Profile 0.13.0
 
-Do more large file timing tests?
+Look at EAs when unames change.
+
+Examine regress handling of acls/eas/resource forks.
+
+Fix EA/ACL format (waiting on Gruenbacher)
+
+Look into that strange regress error July 22nd on
+prog/old/rdiff-backup/testing/testfiles/long...
 
 ---------[ Medium term ]---------------------------------------
 
@@ -12,26 +23,15 @@ Look into sparse file support (requested by Stelios K. Kyriacou)
 
 Look into security.py code, do some sort of security audit.
 
-Don't require increments.<date>.dir files to be setuid/setgid, or
-don't even have the backup files. (Andrew Bressen)
-
 Look at Kent Borg's suggestion for restore options and digests.
 
 Add --list-files-changed-between or similar option, to list files that
 have changed between two times
 
-Add ACL support
-
 Add --dry-run option (target for v1.1.x)
 
 Add # of increments option to --remove-older-than
 
-Make argument shortcut for cstream, or some other bandwidth limiter.
-
-Write configuration file, to make sure settings like --quoting-char,
---windows-time-format, etc., don't change between sessions,
-backup/restoring, etc.
-
 ---------[ Long term ]---------------------------------------
 
 Think about adding Gaudet's idea for keeping track of renamed files.