X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/97e1254a2db20f02405c2883041c0f1d345f3cd7..599dc93c643352ef76d84de0bf9fc25e72e72178:/TODO diff --git a/TODO b/TODO index ad747fb6..f34bed88 100644 --- a/TODO +++ b/TODO @@ -5,16 +5,6 @@ URGENT --------------------------------------------------------------- IMPORTANT ------------------------------------------------------------ -Cross-test versions - - Part of the regression suite should be making sure that we don't - break backwards compatibility: old clients vs new servers and so - on. Ideally we would test the cross product of versions. - - It might be sufficient to test downloads from well-known public - rsync servers running different versions of rsync. This will give - some testing and also be the most common case for having different - versions and not being able to upgrade. use chroot @@ -194,6 +184,7 @@ IPv6 which should just take a small change to the parser code. + Errors If we hang or get SIGINT, then explain where we were up to. Perhaps @@ -210,6 +201,11 @@ Errors explaining why the socket is closed. I'm not sure if this would work, but it would certainly make our messages more helpful. + What happens if a directory is missing -x attributes. Do we lose + our load? (Debian #28416) Probably fixed now, but a test case + would be good. + + File attributes Device major/minor numbers should be at least 32 bits each. See @@ -259,6 +255,12 @@ logging At the connections that just get a list of modules are not logged, but they should be. + If a child of the rsync daemon dies with a signal, we should notice + that when we reap it and log a message. + + Keep stderr and stdout properly separated (Debian #23626) + + rsyncd over ssh There are already some patches to do this. @@ -321,6 +323,36 @@ chmod: the program. For bonus points there would be a test case for the parser. + (Debian #23628) + + +--diff + + Allow people to specify the diff command. (Might want to use wdiff, + gnudiff, etc.) + + Just diff the temporary file with the destination file, and delete + the tmp file rather than moving it into place. + + Interaction with --partial. + + Security interactions with daemon mode? + + (Suggestion from david.e.sewell) + + +Incorrect timestamps (Debian #100295) + + A bit hard to believe, but apparently it happens. + + +Check "refuse options works" + + We need a test case for this... + + Was this broken when we changed to popt? + + PLATFORMS ------------------------------------------------------------ @@ -362,10 +394,44 @@ Memory debugger http://devel-home.kde.org/~sewardj/ +TESTING -------------------------------------------------------------- + +Cross-test versions + + Part of the regression suite should be making sure that we don't + break backwards compatibility: old clients vs new servers and so + on. Ideally we would test the cross product of versions. + + It might be sufficient to test downloads from well-known public + rsync servers running different versions of rsync. This will give + some testing and also be the most common case for having different + versions and not being able to upgrade. + +Test large files + + Sparse and non-sparse + +Mutator program + + Insert bytes, delete bytes, swap blocks, ... + +configure option to enable dangerous tests + +If tests are skipped, say why. + +Test daemon feature to disallow particular options. + +Pipe program that makes slow/jerky connections. + + DOCUMENTATION -------------------------------------------------------- Update README +Keep list of open issues and todos on the web site + +Update web site from CVS + BUILD FARM ----------------------------------------------------------- Add machines