On 2010-02-25 15:13-0800 Alan W. Irwin wrote:
> Want to give git-bisect a try for this case? If so, here are the
> instructions for reproducing the error.
All good ideas are copied. From a google search for svn bisect, it appears
there is now a perl svn-bisect script to do svn bisect plus an "o
On Feb 26, 2010, at 9:27 , Alan W. Irwin wrote:
> On 2010-02-25 15:13-0800 Alan W. Irwin wrote:
>
>> Want to give git-bisect a try for this case? If so, here are the
>> instructions for reproducing the error.
>
> All good ideas are copied. From a google search for svn bisect, it
> appears
> t
On 2010-02-26 09:27-0800 Alan W. Irwin wrote:
All good ideas are copied. From a google search for svn bisect, it appears
there is now a perl svn-bisect script to do svn bisect plus an "official"
svn-bisect script in the works.
I plan to try the perl script for now to see how fast I can come up
On Feb 26, 2010, at 11:19 , Alan W. Irwin wrote:
> (1) Update my local svn repository for PLplot.
I can't resist pointing out that git always has a local repository!
It can't really be called a local copy of *the* repository, but it is
local. :-)
> (2) Write a script to do the steps mentio
On 2010-02-26 11:29-0800 David MacMahon wrote:
>
> On Feb 26, 2010, at 11:19 , Alan W. Irwin wrote:
>
>> (1) Update my local svn repository for PLplot.
>
> I can't resist pointing out that git always has a local repository! It can't
> really be called a local copy of *the* repository, but it is
Nice work, Alan! Bisection is clearly useful regardless of the tool
used to drive it!
On Feb 26, 2010, at 13:34 , Alan W. Irwin wrote:
> Thus, a range of 1024 revisions only requires 10 updates to find
> which revision fails by bisection.
Just to be explicit, it's not just (only!) 10 updates,
As you all know by now, I'm working on Ruby bindings to PLplot. I am
(still) almost ready for a first release. There's always "a few more
things"! :-)
I am currently working on plimagefr support, including pltr support.
I have noticed that the documentation for plimagrfr's pltr parameter
Subject line pretty much says it all.
Initial valgrind output is
==15558== Invalid read of size 8
==15558==at 0x7B6A901: pthread_cond_destroy@@GLIBC_2.3.2 (in
/lib/libpthread-2.7.so)
==15558==by 0x706A2D0: QMutexPrivate::~QMutexPrivate()
(qmutex_unix.cpp:74)
==15558==by 0x7065850: QMu
