On Mon, Jan 21, 2013 at 12:12:43PM +0000, John wrote: > > If you can formulate a decent patch, then learning Gerrit will be a > > walk in the park. In this light, the list isn't terribly concerned > > about those patches that we "miss out on" because someone doesn't want > > to spend the time to learn Gerrit. Personally I view it as a noise > > filter. > > I expect lots of useful contributions (patches, new board configs etc) > simply are not sent because of this. I think that this is NOT sensible, > though it does depend on what amount of "noise" (in the sense of > unwanted/bad patches etc) there is / would be. Here? Very little...
If a person knows how to use git, it shouldn't be hard for him to download and activate a simple hook that'd add Change-Id: to every commit he creates and it's certainly not hard to push the result to a certain URL and branch. And once you understand that the same unique change-id is used by Gerrit to track new versions of the commits, the answer to all the questions about "submitting new versions", and patch series is answered trivially (if you know how to rewrite git history; that's probably a bit "advanced" but actually is very easy with "git rebase -i" (and rewriting a single commit is a well-known "git amend")). It seems that it's git knowledge that some of the potential contributors to OpenOCD lack, not the Gerrit knowledge. But git knowledge is so useful for every kind of project that it certainly makes sense to learn it first, and then using Gerrit becomes nearly trivial. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 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_122412 _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
