Patches get committed when one of the committers review the patch, find nothing wrong with it, and apply it. I'm not in a position to apply any patches currently, but your patch looks good to me. What might help to get this patch applied faster is to provide an example showing broken behavior beforehand, and demonstrating that the behavior is fixed now. Make it easy for the committer to test your patch. Unit tests are even better ways to provide this testing, but I don't think they're required.
Note that it's probably best to post questions like these to the dev mailing list so they don't get lost in the user mailing list. I've redirected my reply to your message to the dev list. I think it's also appropriate to mention the availability of the patch again on the dev list if you don't hear anything after a week. On 8/17/07, kindsol <[EMAIL PROTECTED]> wrote: > I have submitted a new patch to > https://issues.apache.org/jira/browse/TOMAHAWK-83 because > the existing patches were out of date with the head. > > So I am wondering, how do submitted patches get committed? > > Thanks for any guidance. > > > -Sol > >
