It applies... Patches, bug reports etc should always got to a Jira ticket. This allows us to track the patch and any discussion along with it. Also if for whatever reason there are multiple iterations of a patch prior to it being committed it can be seen there K On 4/11/12 8:44 AM, "Patrick Lists" <freeswitch-list@puzzled.xs4all.nl> wrote:
On 04/11/2012 03:34 PM, Philip.Pirozhkov@ontarget-group.com wrote:
Sorry for being stupid and confusing everyone, ESL luamod builds fine. But ESL rubymod build from mainline fails, and my patch fixes that. It would be very nice to apply it upstream.
Although this is the -dev list and not the -users list I'm assuming that the way to handle patches is still the same: please create a ticket on Jira and attach the patch.
If the guideline of creating a Jira for patches does not apply to the -dev list then please accept my apologies for the noise.
Regards, Patrick
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org