Re: [asterisk-dev] Questions on feature/patch process

2019-04-08 Thread Dan Cropp
Thanks again Joshua -Original Message- From: asterisk-dev On Behalf Of Joshua C. Colp Sent: Monday, April 8, 2019 5:16 AM To: asterisk-dev@lists.digium.com Subject: Re: [asterisk-dev] Questions on feature/patch process On Fri, Apr 5, 2019, at 7:05 PM, Dan Cropp wrote: > > I sub

Re: [asterisk-dev] Questions on feature/patch process

2019-04-08 Thread Dan Cropp
Thank you Florian From: asterisk-dev On Behalf Of Floimair Florian Sent: Monday, April 8, 2019 2:46 AM To: Asterisk Developers Mailing List Subject: Re: [asterisk-dev] Questions on feature/patch process Yes, you need to cherry-pick your patch to branch 16. You can do this directly in gerrit

Re: [asterisk-dev] Questions on feature/patch process

2019-04-08 Thread Joshua C. Colp
On Fri, Apr 5, 2019, at 7:05 PM, Dan Cropp wrote: > > I submitted a patch to git review earlier this week. I submitted it > based on master branch for the issue I worked on. > > If we would like this to be part of a future asterisk 16 version, do I > need to do any additional work for this

Re: [asterisk-dev] Questions on feature/patch process

2019-04-08 Thread Floimair Florian
ag von Dan Cropp Antworten an: Asterisk Developers Mailing List Datum: Samstag, 6. April 2019 um 00:05 An: Asterisk Developers Mailing List Betreff: [asterisk-dev] Questions on feature/patch process I submitted a patch to git review earlier this week. I submitted it based on master

[asterisk-dev] Questions on feature/patch process

2019-04-05 Thread Dan Cropp
I submitted a patch to git review earlier this week. I submitted it based on master branch for the issue I worked on. If we would like this to be part of a future asterisk 16 version, do I need to do any additional work for this using asterisk 16 as the source branch? Also, I have code to