Adding upstream version 1.6~pre2.upstream/1.6_pre2

Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>

3 files changed, 27 insertions, 25 deletions

diff --git a/doc/lzip.1 b/doc/lzip.1
index a1a7591..bcd4c5a 100644
--- a/doc/lzip.1
+++ b/doc/lzip.1
@@ -1,7 +1,7 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.36.
-.TH LZIP "1" "April 2009" "Lzip 1.6-pre1" "User Commands"
+.TH LZIP "1" "May 2009" "Lzip 1.6-pre2" "User Commands"
 .SH NAME
-Lzip \- manual page for Lzip 1.6-pre1
+Lzip \- manual page for Lzip 1.6-pre2
 .SH SYNOPSIS
 .B lzip
 [\fIoptions\fR] [\fIfiles\fR]
diff --git a/doc/lzip.info b/doc/lzip.info
index d40f84f..e1e5029 100644
--- a/doc/lzip.info
+++ b/doc/lzip.info
@@ -11,7 +11,7 @@ File: lzip.info,  Node: Top,  Next: Introduction,  Up: (dir)
 Lzip
 ****
 
-This manual is for Lzip (version 1.6-pre1, 27 April 2009).
+This manual is for Lzip (version 1.6-pre2, 21 May 2009).
 
 * Menu:
 
@@ -67,11 +67,12 @@ also split the compressed output in volumes of a given size, even when
 reading from standard input. This allows the direct creation of
 multivolume compressed tar archives.
 
-   The amount of memory required for compression is about 2 times the
-dictionary size limit plus 8 times the dictionary size really used. For
-decompression is a little more than the dictionary size really used.
-Lzip will automatically use the smallest possible dictionary size for
-each member without exceeding the given limit. It is important to
+   The amount of memory required for compression is about 5 MiB plus 1
+or 2 times the dictionary size limit (1 if input file size is less than
+dictionary size limit, else 2) plus 8 times the dictionary size really
+used. For decompression is a little more than the dictionary size really
+used. 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.
 
@@ -558,15 +559,15 @@ Concept Index
 
 Tag Table:
 Node: Top224
-Node: Introduction967
-Node: Algorithm4208
-Node: Invoking Lzip6434
-Node: File Format10781
-Node: Examples12735
-Node: Lzdiff14568
-Node: Lzgrep15887
-Node: Lziprecover16922
-Node: Problems17619
-Node: Concept Index18144
+Node: Introduction965
+Node: Algorithm4288
+Node: Invoking Lzip6514
+Node: File Format10861
+Node: Examples12815
+Node: Lzdiff14648
+Node: Lzgrep15967
+Node: Lziprecover17002
+Node: Problems17699
+Node: Concept Index18224
 
 End Tag Table
diff --git a/doc/lzip.texinfo b/doc/lzip.texinfo
index f29b29e..87e223f 100644
--- a/doc/lzip.texinfo
+++ b/doc/lzip.texinfo
@@ -5,8 +5,8 @@
 @finalout
 @c %**end of header
 
-@set UPDATED 27 April 2009
-@set VERSION 1.6-pre1
+@set UPDATED 21 May 2009
+@set VERSION 1.6-pre2
 
 @dircategory Data Compression
 @direntry
@@ -84,11 +84,12 @@ compressed output in volumes of a given size, even when reading from
 standard input. This allows the direct creation of multivolume
 compressed tar archives.
 
-The amount of memory required for compression is about 2 times the
-dictionary size limit plus 8 times the dictionary size really used. For
-decompression is a little more than the dictionary size really used.
-Lzip will automatically use the smallest possible dictionary size for
-each member without exceeding the given limit. It is important to
+The amount of memory required for compression is about 5 MiB plus 1 or 2
+times the dictionary size limit (1 if input file size is less than
+dictionary size limit, else 2) plus 8 times the dictionary size really
+used. For decompression is a little more than the dictionary size really
+used. 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.