diff options
| author | Daniel Baumann <mail@daniel-baumann.ch> | 2015-11-07 11:52:38 +0000 |
|---|---|---|
| committer | Daniel Baumann <mail@daniel-baumann.ch> | 2015-11-07 11:52:38 +0000 |
| commit | d296515f4777d1e4b7d78e6aa8ea698162bfbc2b (patch) | |
| tree | 3a4ce9f245a9eb30538daa0b9b62c16146d9ad0e /doc/lziprecover.texi | |
| parent | Adding debian version 1.17-1. (diff) | |
| download | lziprecover-d296515f4777d1e4b7d78e6aa8ea698162bfbc2b.tar.xz lziprecover-d296515f4777d1e4b7d78e6aa8ea698162bfbc2b.zip | |
Merging upstream version 1.18~pre1.
Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
Diffstat (limited to '')
| -rw-r--r-- | doc/lziprecover.texi | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/lziprecover.texi b/doc/lziprecover.texi index 3f6e0aa..29045e7 100644 --- a/doc/lziprecover.texi +++ b/doc/lziprecover.texi @@ -6,8 +6,8 @@ @finalout @c %**end of header -@set UPDATED 28 May 2015 -@set VERSION 1.17 +@set UPDATED 30 June 2015 +@set VERSION 1.18-pre1 @dircategory Data Compression @direntry @@ -302,9 +302,9 @@ The only remedy for total device failure is storing backup copies in separate media. How does lzip compare with gzip and bzip2 with respect to data safety? -Lets suppose that you made a backup copy of your valuable scientific -data, compressed it, and stored two copies on separate media. Years -later you notice that both copies are corrupt. +Lets suppose that you made a backup of your valuable scientific data, +compressed it, and stored two copies on separate media. Years later you +notice that both copies are corrupt. If you compressed with gzip and both copies suffer any damage in the data stream, even if it is just one altered bit, the original data can't |