I think it is necessary to add the notice to UPDATING because it's been
half an year since the incident day. If it were like within last few
days, I definitely would've gotten some hints about the fix by scanning
-current (which I did). But I had to scratch my heads helplessly until
I asked the list, and you know that the typical response of the list to
this type of inquiry has been `Welcome to Yesterday.' If UPDATING does
not properly save people like me, what will?
So, Warner, could you update the relevant entry in UPDATING?
On Sat, Dec 01, 2001 at 10:43:39PM +0100, Anton Berezin wrote:
> On Sat, Dec 01, 2001 at 01:26:11PM -0800, Eugene M. Kim wrote:
> > Oh, never mind. I just re-read the thread you pointed (thanks) and
> > saw it affects the systems *installed around the breakage date*.
> > UPDATING does not mention about this fact (it simply says `Building
> > perl was broken'); perhaps it should be updated to mention the
> > misfortune of the installed system and the link to the fix; Warner?).
> Well, that would definitely be a good idea half a year ago. Nowadays, I
> doubt there will be any significant number of unlucky souls having
> operating -current systems built between May 1st and May 2nd. You might
> be unique at that. ;-)
> | Anton Berezin | FreeBSD: The power to serve |
> | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org |
> | [EMAIL PROTECTED] (_(_|| | [EMAIL PROTECTED] |
> | +45 7021 0050 | Private: [EMAIL PROTECTED] |
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message