Re: Submitting a patch to Kannel: best practices?

Hi,

Usually people just post the patch to the devel list with subject: Patch:
<filename>. Patch is attached as a diff of the file(s) from latest svn
sources, followed by a brief description in the body.

Wrt to your proposed solution, I am not very much in favor. In bearerbox
this is handle on the fly through its admin HTTP interface. I think a
similar approach would be best for smsbox.

BR,
Nikos

On Fri, Dec 17, 2010 at 8:10 AM, David McCann <[email protected]>wrote:

> Greetings all!
>
> I've been a kannel user for years, but within the past week I've just
> started to work directly with the code.  I had a particular need which I
> couldn't find a good workaround for:
>
> My current deployment with kannel uses whitelisting to dispatch messages to
> various running web applications (at the sms-service group level), however
> users do update their contact information from time to time, meaning the
> whitelist needs to updated, preferrably without the smsbox having to be
> restarted entirely.
>
> I've added a new command to the list of available commands for SMSBox,
> namely /cgi-bin/refreshlist, and (maybe a little overzealously) created an
> issue: https://redmine.kannel.org/issues/584
>
> And submitted my patch there.
>
> Given that I'm pretty new to this community, I'm wondering if anyone can
> advise me on the best/most convenient way to submit a patch for
> incorporation into the code?
>
> Thanks in advance,
> David McCann
> T4D, UNICEF Uganda
>
>