> Is a new README file safe enough to go into 5.2? Yes. Traditionally, we always tended to tweak the documentation right up to the last minute. In particular, I've sometimes done a blitz on the mailing lists to garner material for an update to the FAQ. (That won't happen this time - we've got an anniversary service at church, so I'm up to my eyeballs in putting together displays of the history of the place. Not to mention That Bloody Book).
The main thinking behind the code freeze is to avoid us breaking the code just before it goes out. Screwing up the documentation would be much less disasterous! :-) (Not least because no-one ever looks at it anyway.....) I'd like to add a new one, > README.mibs, which summarizes what MIBs are available. It's a first hack and > probably has some inaccuracies, but it's a start. Available here, for the > moment: > > http://www.net-snmp.org/unsupported/README.mibs Yup - that looks extremely useful! I've slight reservations about the name though - we already have a "README.mibs" file (in the mibs directory). It might be better to use a different name for this. Maybe something which indicates that this lists what MIBs the agent supports? Bruce> I dont' see what the "available" column is buying you. No - I think it's useful. If nothing else, it indicates that we know about this particular group. We *know* that it's not been implemented, rather than having simply overlooked it. Dave ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
