In bisect-runner.pl's synopsis, the test program must be outside the cwd.

Karl notes that the previous version, using C<test_prog.pl>, wrongly
suggests that a test program can be in the git checkout used for
bisecting. This won't work for an untracked file, because bisect.pl's first
sanity check will spot it and refuse to run. For a tracked file (such as an
existing test script in t), things may be far more confusing, as
bisect-runner.pl will end up running the current version for the revision
tested, instead of the version for the revision checked out at start time.

diff --git a/Porting/bisect-runner.pl b/Porting/bisect-runner.pl
index 1991130..cc04895 100755 (executable)
--- a/Porting/bisect-runner.pl
+++ b/Porting/bisect-runner.pl
@@ -100,7 +100,7 @@ bisect.pl - use git bisect to pinpoint changes
     # When did this start matching?
     .../Porting/bisect.pl --expect-fail --match '\buseithreads\b'
     # When did this test program stop working?
-    .../Porting/bisect.pl -- ./perl -Ilib test_prog.pl
+    .../Porting/bisect.pl -- ./perl -Ilib ../test_prog.pl
     # When did this first become valid syntax?
     .../Porting/bisect.pl --target=miniperl --end=v5.10.0 \
          --expect-fail -e 'my $a := 2;'