2013/1/18 CeDeROM <[email protected]>: > On Thu, Jan 17, 2013 at 11:20 PM, Laurent Gauch > <[email protected]> wrote: >>> Multi-billion companies have used your approach for their work on the >>> Linux kernel and all they get for it is ridicule by everyone with >>> half a clue in the kernel community. >> bla bla bla . You cannot compare Linux and OpenOCD. Linux is now mature >> and it is natural to have only small patches in the kernel. >> But what about the begin of Linux ? I am not sure there were only small >> patches. >
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..... 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. 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 ? I know it is a lot of work to review patch and it's a lot of responsibility to apply patches to the OpenOCD master branch as we don't want to break something. However, error is human, if a patch breaks something then we can fix it. Best regards, Franck. ------------------------------------------------------------------------------ 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
