>> Nice work Zach. >> > > Thanks Dick. But nothing else for me to add? :) >
Yes, I would ask that folks *try* out the CMake support. I think they have the potential to help some Windows folks who might get roadblocked at cygwin requirements. > >> Maybe this file can be put into the top dir of the repository so it can >> evolve more easily than it can by reworking deleted email messages. >> >> Is this a good idea? The problem then is that the only way to evolve it >> is to submit a patch? >> > > You are not the first to ask, but we think alike: > > > https://lists.berlios.de/pipermail/openocd-development/2009-April/005561.html > > In short, I would rather have the freedom to rework an e-mail than feel > the cold, clammy, cumbersome constraint of my present patching process. > Agreed entirely, email is better than this constraint. But I think there are other options to consider: a wiki, a text file on a facebook page, a google app site, or the trackers at the berlios site. Any of these are superior because there is only *one copy* out there at any moment, and we don't have to look for it. google apps, found at http://google.com/a has some neat stuff for free there. You can even concurrently edit a text file over the internet with somebody else located elsewhere. Might be a way to resolve a questionable piece of code. It also stores documents, so we could simply set up the document there. Dick _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
