Previously Anthony Towns wrote:
> This bug appears to have been introduced when flag_unresolved_error was
> added in 2.4.7, and the trivial fix of making flag_unresolved_error a
> static and defining it out if the #ifdef should work perfectly (since
> flag_unresolved_error is not referred to outsid
Previously Anthony Towns wrote:
> This bug appears to have been introduced when flag_unresolved_error was
> added in 2.4.7, and the trivial fix of making flag_unresolved_error a
> static and defining it out if the #ifdef should work perfectly (since
> flag_unresolved_error is not referred to outsid
On Sat, Aug 18, 2001 at 11:48:43PM +0200, Wichert Akkerman wrote:
> Previously Anthony Towns wrote:
> > What's being done to fix this bug? When will it be fixed? Etc?
> Waiting for upstream.
That sounds an awful lot like "nothing" and "no idea", respectively.
This bug appears to have been introdu
Previously Anthony Towns wrote:
> What's being done to fix this bug? When will it be fixed? Etc?
Waiting for upstream.
Wichert.
--
_
/ Nothing is fool-proof to a sufficiently talented fool \
| [EMAIL PROTECTED]
4 matches
Mail list logo