On Sat, Apr 5, 2014 at 4:46 PM, Paul Belanger <[email protected]>wrote:
> On Sat, Apr 5, 2014 at 2:58 AM, Olle E. Johansson <[email protected]> wrote: > > > > On 04 Apr 2014, at 20:32, SVN commits to the Digium repositories < > [email protected]> wrote: > > > >> - case 'I': > >> - ast_set_flag(&ast_options, > AST_OPT_FLAG_INTERNAL_TIMING); > >> - break; > > > > Just checking... I would rather add a NOTICE log here that "i" is not > needed any more. Please make sure that configurations starting with "- i" > will not suddenly fail. > > > I agree with Olle here, this seems to be a massive change mid-release. > Removing a command-line option is certainly going to break some > peoples boxes. Why not a deprecated warning and then removal from > trunk to give people time to react? > FWIW, specifying this command line option or asterisk.conf option, even after it has been removed, should be fine. It will just be ignored and no new warnings will be generated, AFAICT. On the surface, this looks like a change that shouldn't be made in a release branch. However, this really is an option that should have never existed. It's never the right thing to turn it off. The change to make it the only way it works is really the right thing to do. It was equivalent to an option called "make_things_work_properly=yes". -- Russell Bryant
-- _____________________________________________________________________ -- 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
