Hi Max.
Max Baker wrote:
Hey Alex,
Your break down of the regex should help me figure out why I changed it. I'll let you know what I find.
It's too late for 5.2, so probably 5.2.1, 5.1.3. If the change is in 5.0.9, then the fix can go into 5.0.10 also.
I guess it didn't quite make it into 5.2.1. Let me know if you would like me to submit another patch with my suggested changes. (Move the regex to a sub and call that sub from all spots)
Sorry, I forgot all about it.. Can you please submit a patch to the patch repository? I can then do some testing and if it's ok I'll put it in. Hopefully I can discover quickly why I made the change in the first place!
Thanks
Alex
Cheers, -m
On Tue, Nov 16, 2004 at 09:45:11PM -0500, Alex Burger wrote:
Hi Max.
Your break down of the regex should help me figure out why I changed it. I'll let you know what I find.
It's too late for 5.2, so probably 5.2.1, 5.1.3. If the change is in 5.0.9, then the fix can go into 5.0.10 also.
Thanks
Alex
Max Baker wrote:
On Tue, Nov 16, 2004 at 08:31:20PM -0500, Alex Burger wrote:
Hi Max.
That was my change. See patch 722075. I can't remember exactly why I made the change, but I do remember changing it. I'll have to dig into it a bit more to figure out what the reason was..
Thanks Alex,
Let me know if there is something I can do to help. When we fix this, what version do you think this will end up in?
-m
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
