What paritosh says is correct. Each time you make significant progress, update against trunk and post a new version of the patch with the same name.
It is also common for somebody to publish their work in progress on github. I often even rebase my changes to keep them on top of trunk changes when using github. On Sat, Feb 11, 2012 at 6:43 AM, Paritosh Ranjan <[email protected]> wrote: > Submitting a patch code would work. > I don't understand what do you mean by "refresh the patch". > > You can add new incremental patches on the same jira issue. > If you keep the name of all the patches MAHOUT-976, then jira can identify > the latest patch by graying out the older ones. > > Paritosh > > > On 11-02-2012 19:32, Herta, Christian wrote: > >> At moment I write new code for mahout (MLP - seeMAHOUT-976 >> [https://issues.apache.org/**jira/browse/MAHOUT-976<https://issues.apache.org/jira/browse/MAHOUT-976>] >> ). I wonder how to contribute >> "work-in-progess". Should I prepare a patch for new code and refresh the >> patch >> continuously? >> Christian >> > >
