| | 1 | -*- indented-text -*- |
| | 2 | |
| | 3 | URGENT --------------------------------------------------------------- |
| | 4 | |
| | 5 | |
| | 6 | IMPORTANT ------------------------------------------------------------ |
| | 7 | |
| | 8 | Cross-test versions |
| | 9 | |
| | 10 | Part of the regression suite should be making sure that we don't |
| | 11 | break backwards compatibility: old clients vs new servers and so |
| | 12 | on. Ideally we would test the cross product of versions. |
| | 13 | |
| | 14 | It might be sufficient to test downloads from well-known public |
| | 15 | rsync servers running different versions of rsync. This will give |
| | 16 | some testing and also be the most common case for having different |
| | 17 | versions and not being able to upgrade. |
| | 18 | |
| | 19 | |
| | 20 | NICE ----------------------------------------------------------------- |
| | 21 | |
| | 22 | rsyncsh |
| | 23 | |
| | 24 | Write a small emulation of interactive ftp as a Pythonn program |
| | 25 | that calls rsync. Commands such as "cd", "ls", "ls *.c" etc map |
| | 26 | fairly directly into rsync commands: it just needs to remember the |
| | 27 | current host, directory and so on. We can probably even do |
| | 28 | completion of remote filenames. |
| | 29 | |
Matt McCutchen's Web Site / rsync / rsync.git / blame_incremental