Hi, Alan, On Feb 25, 2010, at 13:47 , Alan W. Irwin wrote:
> I am > not sure whether it is a regression caused by the embedded blank > fix or a > regression caused by a previous -dev tk fix, but -dev tk (as run by > the > test_interactive target) used to work fine for the CMake-based > build system > for the installed examples. I can't help you with the tk problem, but wanted to note that this kind of situation is exactly why "git bisect" was created: finding the exact commit that breaks something. You start off by giving "git bisect" the last known good version and the currently known bad version and it checks out a version "in the middle". You build/test that version, tell "git bisect" whether it is good or bad, and it then checks out a version "in the middle" of the updated known-good/ known-bad range. The process repeats until the exact change which introduces the problem is identified. If you can automate/script the build/test steps, then git can iterate to the end without any intervention! Sorry for the off-topic advocacy, Dave ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
