diff options
author | Lars Wirzenius <liw@liw.fi> | 2016-07-14 20:15:00 +0300 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2016-07-14 20:15:00 +0300 |
commit | 60515b73681bdb08967437e1f808b8547ad9d66b (patch) | |
tree | 72130fa146fde4e2642a5d92451fdd184d7d09e7 /yarn.1.in | |
parent | e1b75cdebf020b888620a11c7e3f2827430ccb8c (diff) | |
download | cmdtest-60515b73681bdb08967437e1f808b8547ad9d66b.tar.gz |
Fix yarn manpage to say DATADIR instead of TESTDIR
Diffstat (limited to 'yarn.1.in')
-rw-r--r-- | yarn.1.in | 18 |
1 files changed, 9 insertions, 9 deletions
@@ -62,21 +62,21 @@ The backup scenario from above might be implemented as follows: .IP .nf IMPLEMENTS GIVEN some live data in a directory -rm -rf "$TESTDIR/data" -mkdir "$TESTDIR/data" -echo foo > "$TESTDIR/data/foo" +rm -rf "$DATADIR/data" +mkdir "$DATADIR/data" +echo foo > "$DATADIR/data/foo" .IP IMPLEMENTS GIVEN an empty backup repository -rm -rf "$TESTDIR/repo" -mkdir "$TESTDIR/repo" +rm -rf "$DATADIR/repo" +mkdir "$DATADIR/repo" .IP IMPLEMENTS WHEN a backup is made -backup-program -r "$TESTDIR/repo" "$TESTDIR/data" +backup-program -r "$DATADIR/repo" "$DATADIR/data" .IP IMPLEMENTS THEN the data can be restored -mkdir "$TESTDIR/restored" -restore-program -r "$TESTDIR/repo" "$TESTDIR/restored" -diff -rq "$TESTDIR/data" "$TESTDIR/restored" +mkdir "$DATADIR/restored" +restore-program -r "$DATADIR/repo" "$DATADIR/restored" +diff -rq "$DATADIR/data" "$DATADIR/restored" .IP IMPLEMENTS FINALLY cleanup echo nothing to do, actually |