> As for the topic, it's nice that Øyvind decided to stop for now, but > in the meantime we have broken code in head.
What did you have in mind? (performance regression is known, will be addressed next week, and there is possibly an assert lurking, but other than that there are no known regressions) > I think the best would be > to revert to a known working version and Øyvind could try again when > he got everything figured out. The versions are there in svn, they are not gone. > Also, one big patch for such change > would be better than dozens of small ones IMO (yes, I know that it's > against the local "tradition"). Actually numerous small patches is what allows bisection to work. I think it would be a *bad idea* to make one big patch for something like this even in a dev branch. Zach opened a thread to collect opinions on how OpenOCD should be run, you could post a proposal there... -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
