James Carlson wrote:
Rick Jones writes:
OK, but I reserve the right to revert it if the bug isn't fixed in an undefined
"reasonable" timeframe :)
Sounds like the right answer.
I've bumped it to a P2 and moved it over to the group responsible. I
think it's at least priority 2 because (a) it could easily represent a
portability hazard and (b) it was previously thought fixed.
Being unversed in the ways of checking bug status, and having come across this
thread while preparing an end-of-year status report, I thought I might ask what
the status might be. The bug ID is 6847733.
happy benchmarking,
rick jones
_______________________________________________
networking-discuss mailing list
[email protected]
