[asterisk-dev] [svn-commits] crichter: branch 1.2 r72087 - /branches/1.2/channels/misdn/

[Christian]

> The real problem here is that the more code you change the higher the 
> chances are that it will break something in some horrible way.
>
>   
I am totally aware of this possibility.

But what shall i do when the current code runs on "normal" load but 
breaks on high load ? I think it's worth fxing such problems especially 
on release branches, what do you think ?
> My current pet peeve is the code change that happened somewhere between 
> 1.2.15 and 1.2.17 that caused asterisk to SEGFAULT when running 
> app_macro under some situations.  The change should not have caused 
> that, but it did.    That bug was fixed in 1.2.19, IIRC.
>
>   
yeah .. i know that one too ;)

> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
>