bug#32415: closed (Possible bug in gzip 1.8)

[GNU bug Tracking System]

Your message dated Sun, 25 Dec 2022 21:49:44 -0800
with message-id <15c6abbb-de1d-7877-1066-b8f8a1f7c783@cs.ucla.edu>
and subject line Re: bug#32415: Possible ug in gzip 1.8
has caused the debbugs.gnu.org bug report #32415,
regarding Possible bug in gzip 1.8
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
32415: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32415
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Possible ug in gzip 1.8
>
>
>
>
> Date: 
>
> Fri, 10 Aug 2018 11:52:50 -0400
>
>
>
>
> Hi,
>    We had used gzip routinely to compress and expand text files. 
>
>  We were working on a data set of 93 Mb in files of ~800,000 characters
> each.  We found both one or two characters added or removed from a
> file. 
>
>    Has this been seen before?   Is there a fix?
> -- 
>
>
>
>   
>   
>
>
> Thomas N. Massey
>
> massey@ohio.edu
>
> http://inpp.ohiou.edu/~massey
>
> (Office) (740)593-0933
>
> (Cell)(740)707-1073
>
> (FAX)(740)593-1436
>
>
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#32415: Possible ug in gzip 1.8
>
>
>
>
> Date: 
>
> Sun, 25 Dec 2022 21:49:44 -0800
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
>
>
>
>
> On 8/10/18 14:02, Paul Eggert wrote:
> > What platform and gzip version are you using, and how was gzip built 
> > and installed? Can you reproduce the problem? Better yet, can you show 
> > us how to reproduce the problem?
>
> No further comment in four years, so I'm closing this old bug report.
>
>
>
> --- End Message ---