[OpenSIPS-Devel] [OpenSIPS/opensips] b8d86c: Fix spelling
Branch: refs/heads/master Home: https://github.com/OpenSIPS/opensips Commit: b8d86c6b933cf1833f98c46a32fea4c5c183be53 https://github.com/OpenSIPS/opensips/commit/b8d86c6b933cf1833f98c46a32fea4c5c183be53 Author: Norm Brandinger n.brandin...@gmail.com Date: 2014-09-24 (Wed, 24 Sep 2014) Changed paths: M modules/rr/rr_mod.c Log Message: --- Fix spelling ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] 535601: Fix spelling in Makefile messages
Branch: refs/heads/1.11 Home: https://github.com/OpenSIPS/opensips Commit: 535601a3d3cde62eb4b440979bf1d842b33beb30 https://github.com/OpenSIPS/opensips/commit/535601a3d3cde62eb4b440979bf1d842b33beb30 Author: Norm Brandinger n.brandin...@gmail.com Date: 2014-06-30 (Mon, 30 Jun 2014) Changed paths: M Makefile.conf.template Log Message: --- Fix spelling in Makefile messages ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] de01e4: dialog module - correct spelling in documentation
Branch: refs/heads/master Home: https://github.com/OpenSIPS/opensips Commit: de01e4cd4a0e68f5d76539712119a8da37375438 https://github.com/OpenSIPS/opensips/commit/de01e4cd4a0e68f5d76539712119a8da37375438 Author: Norm Brandinger n.brandin...@gmail.com Date: 2013-10-05 (Sat, 05 Oct 2013) Changed paths: M modules/dialog/README M modules/dialog/doc/dialog_admin.xml Log Message: --- dialog module - correct spelling in documentation ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] 8dbef2: route.c - correct spelling
Branch: refs/heads/master Home: https://github.com/OpenSIPS/opensips Commit: 8dbef294e7170fb1d3ca3a665c3b126c0b76ae31 https://github.com/OpenSIPS/opensips/commit/8dbef294e7170fb1d3ca3a665c3b126c0b76ae31 Author: Norm Brandinger n.brandin...@gmail.com Date: 2013-10-05 (Sat, 05 Oct 2013) Changed paths: M route.c Log Message: --- route.c - correct spelling ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] 34fe50: pike: correct spelling
Branch: refs/heads/1.10 Home: https://github.com/OpenSIPS/opensips Commit: 34fe50129b38df30dbd67250495333e164d3b26c https://github.com/OpenSIPS/opensips/commit/34fe50129b38df30dbd67250495333e164d3b26c Author: Norm Brandinger n.brandin...@gmail.com Date: 2013-08-14 (Wed, 14 Aug 2013) Changed paths: M modules/pike/README M modules/pike/doc/pike_admin.xml Log Message: --- pike: correct spelling (cherry picked from commit 879eacbb5e2f90f1dba2f9b23165e725a5c754d4) ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Business] OpenSIPS 2.0 code release available
Congratulations ! Norm On 2/17/11 7:30 AM, Bogdan-Andrei Iancu wrote: Hi all, After like one year of heavy development, I'm proud to announce the first code release of OpenSIPS 2.0 . This is a version still under heavy development, with limited capability and functionality. For all details (what can do, how to use, where to get), visit: http://www.opensips.org/Development/NewDesignStage1 This is not a production-suitable version, but I want to encourage people to download, compile, test and analyse it as much as possible. Any feedback or comments on the code, approached with used, etc, are more than welcome. Also, I would like to publicly give all the credits for this work to : * Andrei DRAGUS - and...@opensips.org * Bogdan IANCU - bog...@opensips.org * Vlad PAIU - vladp...@opensips.org Waiting for your feedback :) Best regards, Bogdan ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RFC] What repo to use for 2.0 ?
I have found that the speed of mercurial seems to be an issue with larger sized project. For example, try downloading adium: hg clone http://hg.adium.im/adium My vote is for git. Regards, Norm Bogdan-Andrei Iancu wrote: Hi everyone, As we are getting closed to first working code for OpenSIPS 2.0 (a proto core including config, transport, threading, reactor and dispatcher), we will upload the code the public SF repo. I would like to get some feedback from you about what repo type to use - as we have the opportunity to start a fresh new piece of code, we have the option to use a different repo than SVN. SF offers the following options - SVN - git - mercurial - bazaar Should we keep SVN ? pros ? minuses ? something much better ? Regards, Bogdan PS: should we create a poll on the project web site ? ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
