Subject: Re: vi broken currently?
To: None <firstname.lastname@example.org, email@example.com>
From: Feico Dillema <firstname.lastname@example.org>
Date: 11/03/2001 02:20:26
On Fri, Nov 02, 2001 at 08:03:29PM -0500, gabriel rosenkoetter wrote:
> That certainly didn't happen with my 1.5W userland, but I can't
> quite tell whether it's the result of changes to vi (most recently
> on 10/20, seems like someone would have noticed by now) or more
> recently to libc, or maybe (and least likely) because I'm using
> *only* compat I686_CPU on what's actually an AMD Thunderbird?
You can rule that one out. I just build current and see the same, on
an Intel machine without I686_CPU option.