On Dec 12, 2008, at 10:34 AM, Øyvind Harboe wrote:
I'm not enamored of having the zy1000 contents in the repo, but there is no technical reason it must leave. I would like Øyvind to consider moving the zy1000 contents to a separate repository at some future date. In terms of collaboration and merging, having the zy1000 contents elsewhere just means that zy1000 developers submit patches to OpenOCD just like everyone else instead of working in a branch within the same repo but in a differenttop-level project.Trust me when I say that there *IS* collaboration going behind the scenes to push stuff & ideas into OpenOCD. There is plenty of evidence of thisalready in the last year, especially in terms of performance and friendliness towards deeply embedded targets.
Collaboration is great, but having the zy1000 firmware building tools in the openocd repo isn't necessary for that to happen. I'm all for having development branches in the openocd repo. If there is work being done by the zy1000 developers to enhance openocd, it can either be done in a zy1000 repo and the patches submitted via email, or it can be done in an openocd branch directly. Either way, moving zy1000 out of the openocd repo isn't something we need to worry about today. I do have reservations about the precedent it sets for future embedded deployments of openocd, however.
-- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
