1
0
Fork 0

Adding upstream version 1.18~pre1.

Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-21 11:25:32 +01:00
parent f06ff1621d
commit cf6c2d1d59
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
17 changed files with 452 additions and 200 deletions

View file

@ -12,7 +12,7 @@ File: lziprecover.info, Node: Top, Next: Introduction, Up: (dir)
Lziprecover Manual
******************
This manual is for Lziprecover (version 1.17, 28 May 2015).
This manual is for Lziprecover (version 1.18-pre1, 30 June 2015).
* Menu:
@ -274,7 +274,7 @@ files::), if at least one backup copy of the file is made.
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
safety? 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.
@ -652,18 +652,18 @@ Concept index

Tag Table:
Node: Top231
Node: Introduction1208
Node: Invoking lziprecover4304
Node: Data safety9737
Node: Repairing files11666
Node: Merging files13568
Node: File names15409
Node: File format15873
Node: Examples18277
Ref: ddrescue-example19523
Node: Unzcrash20779
Node: Problems23333
Node: Concept index23885
Node: Introduction1214
Node: Invoking lziprecover4310
Node: Data safety9743
Node: Repairing files11667
Node: Merging files13569
Node: File names15410
Node: File format15874
Node: Examples18278
Ref: ddrescue-example19524
Node: Unzcrash20780
Node: Problems23334
Node: Concept index23886

End Tag Table