Robert Story wrote:
> I tend to agree. And if we are going to make this a public global in the
> library, then I strongly suggest we rename it, prefixing with 'netsnmp_trapd'
> or something in that vein...
+1 for the rename, but I still think this change should be trunk only.
IMHO there's not enough benefit here to justify an incompatible change
in a branch. Remember what dist/RELEASE-INSTRUCTIONS has to say:
Note: maintenance releases (eg 5.2.x) should never have changes
that would require current to be incremented.
+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
