On Tue, Oct 14, 2008 at 6:01 AM, John McCarthy <[EMAIL PROTECTED]> wrote: > Hi, > > On Sun, 2008-10-12 at 19:38 +0200, Øyvind Harboe wrote: >> I was not able to apply this patch cleanly. > > I just took the original 2 patches and used 'patch -p0 < xxx.patch' to > apply them to trunk and they applied cleanly. Here is the 'svn diff' > patch of the result. > > I'm really curious why this didn't work for you though.
It worked now. Committed. W.r.t. GIT&SVN this is not about you. I'm not one bit worried about you because you seem to be highly productive anyway ;-) Though it doesn't matter what tools you use as long as the patches: - have a svn # so we know which version you're patching against - they apply with problems - there aren't multiple patches to the same file in different patch files I think GIT is as neat as the next guy, but the rules of the game for OpenOCD is not to make changes without a consensus. Changes include tools, procedures or implementation of OpenOCD... Source control is an especially tricky thing to change as well... my main battle in everyday life is to get developers to use *any* source control. Switching from one to another is a titanic battle... I'm working on a project where RCS is alive and well(with gobs of scripting on top...). I'd like to change that one to CVS, SVN or GIT, but it ain't going to happen because of little me wanting a source control system which is *only* one or two decades old :-) I'd like to use C++ in OpenOCD, but C++ and the people with the deeply embedded skills do not overlap much... it could result in a *very* select group of developers that could work on OpenOCD :-) -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer Free eCos workshop in Oslo October 21! http://www.zylin.com/workshop.html _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
