Post 0.4 release, I'd like to see patches being merged in ascending order of disruptiveness.
Of course it isn't possible to measure disruptiveness, but I think about two things: cherry pickability and impact on design and direction of openocd. This makes patches more cherry pickable(create some private 0.4 + specific bugfixes branch) and reduces mering work... Also, it gives us the most amount of time to discuss any new directions that openocd will move in. -- Øyvind Harboe Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118 http://www.zylin.com/events_embeddedworld.html US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
