Dave Shield wrote: > We've agreed to not fix a bug, because of a concern that the fix is likely > to have greater impact than the bug itself. > That's a judgement call, and may turn out to be the wrong decision. > But it's not an unreasonable position to take.
Exactly. (And I still feel confident it's the right decision.) > It might be worth annotating the "public variable" definitiions in > the 5.4.x line (e.g. in TrapReceiver.xs) , to indicate that it will > disappear in future releases. Similarly, maybe a mention in > the 5.4.x documentation - to warn of the issue, and describe the > short-term and long-term fixes. That'd certainly be helpful (for all active branches rather than just 5.4.x, though). +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
