Ah, that makes sense, once you know about it. :) You might want to add a "how to contribute a patch" sentence to http://gradle.org/contribute so it is easier for potential contributors to find out the way that makes it easiest and most efficient to get a patch accepted.
thanks, Philip On Mon, Mar 26, 2012 at 9:48 AM, Luke Daley <luke.da...@gradleware.com> wrote: > > On 26/03/2012, at 2:46 PM, Philip Crotwell wrote: > >> Great, thanks. >> >> Forgot to mention the patch is attached to the issue in jira. Also >> attaching it here. >> >> http://issues.gradle.org/browse/GRADLE-2084 >> >> For future reference, should patches be sent to the dev mailing list >> or just attached to the jira issue? I was assuming you all would be >> monitoring the issue tracker, but maybe that is not the most efficient >> way? > > The most efficient way is to submit a pull request via GitHub. > > However, if that doesn't work for you then feel free to submit it against an > issue and ping the dev list. > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
