summaryrefslogtreecommitdiffstats
path: root/doc/lziprecover.texi
diff options
context:
space:
mode:
authorDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 11:52:32 +0000
committerDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 11:52:32 +0000
commitde06b1d957bdad592fff87e845d27d40cfcbd694 (patch)
tree38d1a64462988c92f82b12d2ea3dca6864006003 /doc/lziprecover.texi
parentAdding upstream version 1.17. (diff)
downloadlziprecover-de06b1d957bdad592fff87e845d27d40cfcbd694.tar.xz
lziprecover-de06b1d957bdad592fff87e845d27d40cfcbd694.zip
Adding upstream version 1.18~pre1.upstream/1.18_pre1
Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
Diffstat (limited to 'doc/lziprecover.texi')
-rw-r--r--doc/lziprecover.texi10
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