If you don't have time to work on OpenOCD, then I don't have any problems with that. The world is full of smart people who could have, but don't have time to, contribute to OpenOCD.
If you do want to spend some time on OpenOCD, then I urge you to have a look at what Gerrit+Jenkins does for the community. Some of the things that Gerrit+Jenkins does for us: - Contributors, rather than maintainers will do all the work of formulating patches and serving them on a silver platter to the maintainers. - Jenkins will build and check your patch for warnings. If you generate warnings in some of the configurations that Jenkins checks for, you will get an email w/info about that. No other humans will waste time on your patch before it is ready and clean of all nits(warnings, whitespace errors, etc.). - It makes it possible for us to organise the patches, keep track of improved version of patches, etc. and decide when to submit them to the repository with a click of a button. I don't think the maintainers will be accepting or reviewing patches that are not submitted to Gerrit anymore. If this means that we loose those contributors who can't or won't take time time to learn Git and how to configure and us Gerrit, then that's really a non-issue, because maintainers are not going to spend their time to save the contributors this effort. -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 http://www.zylin.com/ _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
