On Mon, May 18, 2009 at 3:28 PM, Øyvind Harboe <oyvind.har...@zylin.com> wrote: > If you post patches and vouch for them, then I, or another committer > who beats me to it, will commit them promptly. > > Currently the problem is that there are patches posted, but nobody > has time to say anything as to whether they are ready for testing. > > I think it would be *greatly* helpful if we could break these changes > into a series of harmless patches and then a final patch to flip > the switch... Keeping all patches small & well understood. > > W.r.t. "vouching", I'm not saying that you should guarantee > that they work, but if you can simply state what testing you did > then we have much better understanding of the expected quality > and robustness of these patches. > > The *real* testing only happens after the patches are committed. That's > just how the OpenOCD community works at this point. >
I broke it down as small as possible. The change is trivial. I tested it here as far as possible. I can't test *all* of the functions as my target doesn't use them, but again, the rewrite is absolutely trivial. Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development