Path: utzoo!attcan!uunet!zephyr.ens.tek.com!tektronix!sequent!ccssrv!ccsrd3!chris
From: chris@ccsrd3.UUCP (Chris Andersen ("The Dangerous Guy"))
Newsgroups: comp.sources.d
Subject: Re: Want perl 3.0 patches 2,3,4
Message-ID: <858@ccsrd3.UUCP>
Date: 24 Nov 89 04:12:36 GMT
References: <940003@hpmwdjm.HP.COM> <1679@ssp15.idca.tds.philips.nl> <2177@prune.bbn.com>
Reply-To: chris@ccssrv.UUCP (Chris Andersen ("The Dangerous Guy"))
Organization: The Danger Patrol
Lines: 30

In article <2177@prune.bbn.com> rsalz@bbn.com (Rich Salz) writes:
}someone else wrote:
}> Are you sure that was due to your vacation? A lot of people didn't see them.
}
}Most likely, then, those people don't read comp.sources.bugs, which is where
}Perl patches are distributed.  I don't think there was widespread message
}lossage, and I know the patches appeared on uunet -- they're still in the
}spool directory as I write this.
}
}The first patch appeared with the perl3.0 distribution in comp.sources.unix,
}and it had detailed explanation that this was the only patch to appear
}here.  It also pointed out that this patch, LIKE ALL OF LARRY'S PATCHES,
}tell you how to get any ones you might be missing.

Okay, I've gotten them now.  Apparently what happened is that patch 2-4 came
in on the same day our news system barfed and I had to reset it, thus wiping
out the spool directory (speaking of which, has anyone ever written a utility
to rebuild the active file from the files in the spool directory?).

What confused me was that patches 2-4 are actually just one complete patch
(i.e. you can't do one without the other two).  I always thought patch #'s
were assigned to the WHOLE patch, not to the individual parts of it.  So when
I saw patch 5 come along when only a few weeks before i'd seen patch 1, well,
I got mighty confused.

Sorry.  My mistake.  You can stop sending me the patches now.
-- 
Chris Andersen (..!{sun,tektronix}!sequent!ccssrv!chris)
Home: (503) 620-4176	Work: (503) 641-8128
"Join the Danger Patrol!"