would you want the patch against trunk or 1.2.1? I wrote it against 1.2.1 but just svn co trunk and massaged it against that tree also. Is there any particular coding standard and/or etc that is prefered and if so, I will clean the patch up to make less work on someone else. I'm getting the mantis account setup so I can cross post there also. Forgive my ignorance on using mantis though...
Which disclaimer would I need to sign? It appears there are two disclaimers (one requiring me to send $1.00). I frankly don't care on the code what happens to it. I just felt others may find it useful. I know it could use some work but just through it together in a few minutes and then another five minutes of debugging we had it running in production. --Robert On Fri, 13 Jan 2006 10:28:00 -0700, Jared Smith wrote: > Thanks for helping out! > > Please post your patch to the bug tracker at http://bugs.digium.com/, > and make sure you have a signed disclaimer on file. This way, it will > be reviewed by the bug marshals, and we can keep track of it. > > (If you'd like to post the bug number back here, then it'll probably get > a little more attention.) > > -Jared _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev