Path: utzoo!attcan!uunet!tank!ncar!asuvax!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!jarthur!spectre.ccsf.caltech.edu!tybalt.caltech.edu!madler
From: madler@tybalt.caltech.edu (Mark Adler)
Newsgroups: comp.sys.next
Subject: Re: Buzzings4
Message-ID: <1990Mar17.173405.20079@spectre.ccsf.caltech.edu>
Date: 17 Mar 90 17:34:05 GMT
References: <1990Mar17.170857.8941@athena.mit.edu>
Sender: news@spectre.ccsf.caltech.edu
Distribution: comp
Organization: California Institute of Technology, Pasadena
Lines: 20


I noticed the problem with the Buzzings4.wn.tar.Z yesterday, sent a note to
Erica, and she reuploaded it to both cs.orst.edu and j.cc.purdue.edu.  She
did not reupload Buzzings4.ps.Z, I suppose since no one had yet reported a
problem with it.

As of about 9:20 a.m. PST on Saturday, cs.orst.edu still has the bad copy
of Buzzings4.wn.tar.Z in pub/next/buzzings, but the good copy can be found
as Buzz4.wn.tar.Z in pub/next/submissions.  Eventually, the one in
submissions will be moved to buzzings.  On j.cc.purdue.edu, both good and
bad copies (Buzz4.wn.tar.Z is the good one) can be found in pub, and
eventually one of them (hopefully the good one) will be moved to
pub/next/BuzzNUG.

Just by the way, this is quite an issue with several very good and very
extensive programming examples.  It's some 50 odd pages long, so I read
mine on the screen instead of killing a few more trees.

Mark Adler
madler@hamlet.caltech.edu