blob: 50204ca41dd5b0767a0c1a780d36205a52982694 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
Look at manual page examples.
Consider adding --datadir option (Jean-Sébastien GOETSCHY)
See if regressing takes too much memory (large directories).
write test case for --calculate-statistics
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.x
Look at EAs when unames change.
Examine regress handling of acls/eas/resource forks.
Look into that strange regress error July 22nd on
prog/old/rdiff-backup/testing/testfiles/long...
---------[ Medium term ]---------------------------------------
Look into sparse file support (requested by Stelios K. Kyriacou)
Look into security.py code, do some sort of security audit.
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 --dry-run option (target for v1.1.x)
Add # of increments option to --remove-older-than
---------[ Long term ]---------------------------------------
Think about adding Gaudet's idea for keeping track of renamed files.
Look into different inode generation techniques (see treescan, Dean
Gaudet's other post).
|
