Woof! On Thu, 25 Jun 2009 13:30:58 -0400, Kevin Thorley <[email protected]> wrote:
> Now, the real trick would be to add some sort of change tracking so we > could have a numeric id that would follow all steps of a change, Check generated files into a local git repository on the sipXconfig system before replication. Every change can be tracked using git log (including diffs). Comments would include which logged in user made the change, what "page" they were on, etc. Alternately, sipXsupervisor would checkin each config file on each system when it gets it for replication. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
