Re: [PATCH] Kannel bug #0000032 otherwise known as kannel's list function naming clashes with latest mysql list function naming
Davy Chan <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Well, it's been about 12 days since I tried to submit the patch but it still has not been acted on by the moderator of the [email protected] mailing list. Are there any other suggestions on how to submit this patch for review? I've already uploaded the patch to the Mantis Bug tracking system. Would it be possible for the reviewer to grab the patch from there instead of waiting for the list moderator to release my 12 day old posting? See ya... d.c. PS: My offer still stands to help admin this list...it looks like resources from Trigenix to support this list are dwindling now that they have been acquired by OpenWave. **>Date: Thu, 06 Jan 2005 20:55:09 +0100 **>From: Stipe Tolj <[email protected]> **>Organization: The Kannel Group **>To: Davy Chan <[email protected]> **>In-Reply-To: <[email protected]> **>Subject: Re: [PATCH] Kannel bug #0000032 otherwise known as kannel's list function naming clashes with latest mysql list function naming **> **>Davy Chan wrote: **> **>>I've submitted a patch for bug #0000032 to the Mantis bug tracking **>>system. It's 381K in size. Should I submit it also to the devel **>>mailing list? **>> **>>This patch does not have the renaming of all "List" structures to **>>"gw_List". If the "list_XXX" to "gw_list_XXX" patch is accepted, **>>then I'll also do the "List" structures patch. **> **>yes, please provide the patch in unified diff format as attachement, not **>inlined. **> **>Mark it via the [PATCH] subject line prefix so developers can review it. **>Since it's quite big, a gziped version may be prefered I guess. ;) **> **>Please explain also what you do inside the patch. Consider those **>explanations as 'helping hand' to those that take time to review your patch **>and vote for commiting. Thanks in advance. **> **>Stipe