summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2019-03-16 06:45:57 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2019-03-16 06:45:57 +0000
commit85afea931c3a021e186e81f55b9d969f14d14e41 (patch)
tree66639fa7ecd0ae38763a9097ceed2a577548623a /README
parentAdding upstream version 0.13. (diff)
downloadtarlz-85afea931c3a021e186e81f55b9d969f14d14e41.tar.xz
tarlz-85afea931c3a021e186e81f55b9d969f14d14e41.zip
Adding upstream version 0.14.upstream/0.14
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'README')
-rw-r--r--README3
1 files changed, 2 insertions, 1 deletions
diff --git a/README b/README
index 3ada513..f1149a2 100644
--- a/README
+++ b/README
@@ -11,7 +11,8 @@ it like any other tar.lz archive. Tarlz can append files to the end of such
compressed archives.
Tarlz can create tar archives with five levels of compression granularity;
-per file, per block (default), per directory, appendable solid, and solid.
+per file (--no-solid), per block (--bsolid, default), per directory
+(--dsolid), appendable solid (--asolid), and solid (--solid).
Of course, compressing each file (or each directory) individually can't
achieve a compression ratio as high as compressing solidly the whole tar