summaryrefslogtreecommitdiff
path: root/updater/bzip2-1.0.3/bzip2.txt
diff options
context:
space:
mode:
Diffstat (limited to 'updater/bzip2-1.0.3/bzip2.txt')
-rw-r--r--updater/bzip2-1.0.3/bzip2.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/updater/bzip2-1.0.3/bzip2.txt b/updater/bzip2-1.0.3/bzip2.txt
index bf895b6..d2deb39 100644
--- a/updater/bzip2-1.0.3/bzip2.txt
+++ b/updater/bzip2-1.0.3/bzip2.txt
@@ -1,6 +1,6 @@
NAME
- bzip2, bunzip2 - a block-sorting file compressor, v1.0.3
+ bzip2, bunzip2 - a block-sorting file compressor, v1.0.6
bzcat - decompresses files to stdout
bzip2recover - recovers data from damaged bzip2 files
@@ -345,14 +345,14 @@ CAVEATS
but the details of what the problem is sometimes seem
rather misleading.
- This manual page pertains to version 1.0.3 of bzip2. Com-
+ This manual page pertains to version 1.0.6 of bzip2. Com-
pressed data created by this version is entirely forwards
and backwards compatible with the previous public
- releases, versions 0.1pl2, 0.9.0, 0.9.5, 1.0.0, 1.0.1 and
- 1.0.2, but with the following exception: 0.9.0 and above
- can correctly decompress multiple concatenated compressed
- files. 0.1pl2 cannot do this; it will stop after decom-
- pressing just the first file in the stream.
+ releases, versions 0.1pl2, 0.9.0, 0.9.5, 1.0.0, 1.0.1,
+ 1.0.2 and above, but with the following exception: 0.9.0
+ and above can correctly decompress multiple concatenated
+ compressed files. 0.1pl2 cannot do this; it will stop
+ after decompressing just the first file in the stream.
bzip2recover versions prior to 1.0.2 used 32-bit integers
to represent bit positions in compressed files, so they