summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 07:47:56 +0000
committerDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 07:47:56 +0000
commit1f98801df36334e9e0d80e3db19247a5c65c9bf4 (patch)
tree89834a124bab1d1fddc206946271a648ba4352d4 /README
parentAdding upstream version 1.7. (diff)
downloadlzip-1f98801df36334e9e0d80e3db19247a5c65c9bf4.tar.xz
lzip-1f98801df36334e9e0d80e3db19247a5c65c9bf4.zip
Adding upstream version 1.8.upstream/1.8
Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 4 insertions, 4 deletions
diff --git a/README b/README
index 6e70de3..bfeffef 100644
--- a/README
+++ b/README
@@ -29,10 +29,10 @@ compressed output in volumes of a given size, even when reading from
standard input. This allows the direct creation of multivolume
compressed tar archives.
-Lzip will automatically use the smallest possible dictionary size for
-each member without exceeding the given limit. It is important to
-appreciate that the decompression memory requirement is affected at
-compression time by the choice of dictionary size limit.
+Lzip will automatically use the smallest possible dictionary size
+without exceeding the given limit. It is important to appreciate that
+the decompression memory requirement is affected at compression time by
+the choice of dictionary size limit.
As a self-check for your protection, lzip stores in the member trailer
the 32-bit CRC of the original data and the size of the original data,