[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-patches
Subject:    [Net-snmp-patches] [ net-snmp-Patches-424295 ] Move date_n_time out of HR-MIB
From:       noreply () sourceforge ! net
Date:       2001-09-14 19:07:12
[Download RAW message or body]

Patches item #424295, was opened at 2001-05-15 10:58
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=312694&aid=424295&group_id=12694

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Harrie Hazewinkel (harrie)
>Assigned to: Wes Hardaker (hardaker)
Summary: Move date_n_time out of HR-MIB

Initial Comment:
HI,

The attached patch should move the date_n_time
function out of the HR-MIB code. It moves into
a seperate file 'date_n_time_utils' under mibgroup.

This enables the date_n_time used by other MIB module
implementations.

----------------------------------------------------------------------

>Comment By: Wes Hardaker (hardaker)
Date: 2001-09-14 12:07

Message:
Logged In: YES 
user_id=76242

I've commited a similar patch to the mainline CVS tree 
that moves the code into snmplib/snmp-tc.c, where it can 
be used by more than just the agent.


----------------------------------------------------------------------

Comment By: Wes Hardaker (hardaker)
Date: 2001-06-13 14:38

Message:
Logged In: YES 
user_id=76242

Right idea, but we should probably move it into the core 
library as a utility function instead.

We should create a snmp_tc file with related TC based 
functions in it.

(note that you forgot to attach the patch to the patch 
database ;-)



----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=312694&aid=424295&group_id=12694

_______________________________________________
Net-snmp-patches mailing list
Net-snmp-patches@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-patches

[prev in list] [next in list] [prev in thread] [next in thread]