> Well, we have a bug report against 6.4, so my inclination is to change
> it in both trees. We know that the current code is broken on at least
> one major platform. I think that outweighs the unproven possibility
> that the other way might be broken somewhere...
OK, I'm not arguing strongly against it, but imho the current code is
not broken on any major *mature* platform :) The glibc2 stuff is fairly
new, and everyone is still working out the details. We apparently
understand the problem, but we haven't seen Oleg's patches to know what
he actually did, whether the patches we are planning fix his problem, or
what the effects are on machines (even of the same type) outside of his
own.
And remember, I'm actually running a linux RH/glibc2 machine at work, so
I'm not just giving it a hard time for sport (hi scrappy!) ;) How about
if I test some patches in the main tree on my work machine before we
commit to the v6.4.x tree?
- Tom
