diff options
| author | Lars Wirzenius <liw@liw.fi> | 2014-01-12 15:56:44 +0000 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2014-01-12 15:56:44 +0000 |
| commit | c2c4cd60ab11bea68f32dcf47744551039c610c4 (patch) | |
| tree | 50bbc0bf1356c72d7061ecebceb01a481dfe328e /yarns/0010-introduction.yarn | |
| parent | d6863c3f7bb3fe019a7a71bfffe58fd532c0a5ab (diff) | |
| download | obnam-c2c4cd60ab11bea68f32dcf47744551039c610c4.tar.gz | |
Remove finished stuff from fixme chapter
Diffstat (limited to 'yarns/0010-introduction.yarn')
| -rw-r--r-- | yarns/0010-introduction.yarn | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/yarns/0010-introduction.yarn b/yarns/0010-introduction.yarn index 9235c21a..95fb939e 100644 --- a/yarns/0010-introduction.yarn +++ b/yarns/0010-introduction.yarn @@ -49,12 +49,6 @@ been implemented. - with encryption * Compression - generate interesting set of test data, backup once -* Encryption - - add-key - - client-keys - - list-keys - - list-toplevels - - remove-key * Lock handling - force-lock * Repository management @@ -66,17 +60,7 @@ been implemented. Open questions: -* how to test compression and encryption? should I re-run all tests - plain, compressed, encrypted, and compressed+encrypted? also, - network tests? do I need some kind of include mechanism for this? - - I can probably manage just fine with a simpler set of sets for - compression, encryption and networking, no need to go over all - the cases that plain backups go through: if things work for - plain, they probably work for the other cases, if those other - cases work at all - - then add regression tests as need be * test accessing live data over sftp * what errors should I test? can I test? -* multiple clients? * different filesystems? run test suite multiple times, and set TMPDIR to point at a particular filesystem each time |