[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lzip-bug] Lzip 1.20-pre2 released
From: |
Timothy Beryl Grahek |
Subject: |
Re: [Lzip-bug] Lzip 1.20-pre2 released |
Date: |
Thu, 28 Sep 2017 07:25:37 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
Hi Antonio,
Compressing an already compressed file is rarely useful, but you can
do it using the option '-F, --recompress':
If I have more questions about this, I will open another thread.
Thanks. What you propose seems like "greedy" reporting; report
everything that went or will go wrong, or may be interesting to know.
I think the norm is to complain only when a problem is found.
I appreciate your observation regarding my proposal and your decision to
act in contrast to it; acting in contrast to it is definitely the most
sensible approach, especially given what you have said.
Thanks again for your help.
Thus far I have installed and used Lzip 1.20 Pre2 on my home machine and
work machine. Both machines have this version installed on both of their
operating systems. My home machine has it installed on Arch Linux x86-64
and Windows 10 using Cygwin, and my work machine has the exact same
configuration. I have run into no problems compressing or decompressing
files on either machine. For example, I was compressing some disk images
at work, and I was compressing and decompressing some files for my
college classes at home and at work. Lzip 1.20 Pre2 appears to be as
stable as Lzip 1.19. This certainly agrees with what you said previously
about the fact that Lzip 1.20 addresses the interface rather than
function when comparing it with Lzip 1.19.
In other words, the testing I have done now, after the first testing I
have done on Lzip 1.20 Pre2, is general day-to-day use testing. When
time permits, next I will do more in depth, detailed testing that will
allow me to provide a more detailed report as to what I have actually
tangibly tested. Of course I will also comment on any day-to-day use I
have done in a more descriptive fashion.
Best regards,
Timothy Beryl Grahek