On 18 January 2013 08:16, Franck Jullien <[email protected]> wrote: > > Hi, > > I'm new to OpenOCD development. I'm currently adding support of > the openrisc CPU to OpenOCD. > > You are talking about submitting small patch in order to reduce the > reviewing process. Fine, you're right. However, in gerrit, there is very > small patches waiting for almost a year..... >
While i admit we are in need of more reviewers most of those patches are awaiting the original dev to comment/update or will never be merged as stated by the review. > As I'm working on openrisc (which is almost ready to submit now), > I know it won't be upstream (or event reviewed) before a very long > time and it doesn't encourage me to continue on some other > OpenOCD development. > I try to review patches as quickly as i can, the cleaner the patch the quicker it tends to get reviewed. For something like openrisc support it is unlikely that any of the main devs have the ability to test, so other than sanity checking we will generally submit most things you upload for review. > Could we have a "next" branch where patch could be applied (after > review of course) then, after some time and test, those patch could > be cherry-picked to master ? > Not sure this would work, and due to the size of OpenOCD would mean more work for the few devs we have. Spen ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
