Mailing List Archive: [Bug 401] lookup() vs mes_lookup() to keep logfiles cleaner under normal conditions

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.quagga.net/show_bug.cgi?id=401

web@pilot.org.ua changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|excessive logging by |lookup() vs mes_lookup() to
|mes_lookup() |keep logfiles cleaner under
| |normal conditions
AssignedTo|ajschorr@alumni.princeton.ed|paul@dishone.st
|u |

------- Additional Comments From web@pilot.org.ua 2007-09-14 12:33 -------
I agree with Andrew, that continuous and sparse code-spaces are better handled
by separate functions. I'm leaving mes_lookup() untouched and switch from
LOOKUP() to lookup() for rtm_type decoding.
Paul, you can consider doing the same for sparse BGP message code arrays or just
close the bug.
Thanks to all.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs