On Apr 22, 2009, at 8:56 AM, Alain M. wrote:
Hi, I am nnew here and it seems that I landed in the middle of a turnmoil... not uncommon in OpenSource and better handled then most :) I am here for 2 primary reasons, let's start: Øyvind Harboe escreveu:We have discussed adding release branches though. Release branches never happened because there was no particular reason to. If the last couple of days are representative for how things are going to be, then perhaps we should reconsider adding release branches.One long standing problem that I have seen with OpenOCD is that most howtos often specify which SVN version to use...My question is: which version should I use as the last stable version???
OpenOCD 0.1.0. We did a release specifically so there would be a stable version.
With a subquestion: I have seen that newer versions have different configuration scripts, which is the last good version before that??
All of the configuration syntax changes were shaken out by 0.1.0. Anything before that will be some magical SVN version. Converting the syntax is relatively easy and frequently unnecessary. I'd suggest starting with 0.1.0 and only moving to SVN if you have a specific problem that has been resolved there.
BTW, I am using OlimexJtgTiny/Turteliser2 and Luminary/CortexM3
There have been some fixes related to Cortex-M3 in SVN, but the code is more unstable in general.
Thanks for the great work, Alain _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
-- 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
