Hi, some time ago Jean-loup, said on [1]http://www.gzip.org/recover.txt
that
"As you can see, all this is not a trivial task, so you should attempt
it only if your data is very valuable. gzip 2.0 will have a new
blocksize option, allowing to recover easily all undamaged blocks after
Jean-loup has not worked on gzip for many years, but I will leave it to the
gzip maintainers here to answer to their future intentions.
However pigz has that ability now with the --independent option, where the
block size defaults to 128K, and can be changed with the --blocksize option.
See htt
tags 31065 notabug
stop
On Wed, Apr 4, 2018 at 4:01 PM, Mark Adler wrote:
> Jean-loup has not worked on gzip for many years, but I will leave it to the
> gzip maintainers here to answer to their future intentions.
>
> However pigz has that ability now with the --independent option, where the
>
Jim,
So gzip has run into a version 2.0 wall. Just out of curiosity, will the next
version be 1.91? 2.0? 1.A?
Mark
> On Apr 4, 2018, at 5:18 PM, Jim Meyering wrote:
>
> tags 31065 notabug
> stop
>
> On Wed, Apr 4, 2018 at 4:01 PM, Mark Adler wrote:
>> Jean-loup has not worked on gzip for m
On Wed, Apr 4, 2018 at 5:54 PM, Mark Adler wrote:
> So gzip has run into a version 2.0 wall. Just out of curiosity, will the next
> version be 1.91? 2.0? 1.A?
I might have blindly chosen 1.10, since most are used to
version-sorting for such numbers. But these version-number-lengthening
events do
