- (dtucker) [regress/README.regress] Add detail on how to run a single

   test from the top-level Makefile.

diff --git a/ChangeLog b/ChangeLog
index 451cccb17fa2b37e068e3fda1fb41284e781bb81..65d687cd21f035507c452df1552c3b79a5001b05 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -10,6 +10,8 @@
    - djm@cvs.openbsd.org 2004/06/17 14:53:27
      [regress/multiplex.sh]
      shared connection env passing regress test
+ - (dtucker) [regress/README.regress] Add detail on how to run a single
+   test from the top-level Makefile.
 
 20040617
  - (dtucker) [regress/scp.sh] diff -N is not portable (but needed for some

diff --git a/regress/README.regress b/regress/README.regress
index f449bcd154bf8ceb348f7f93e038c924a3420bf1..86b2ceb6d5e78138b8e4f1ae2b3f6b263a05e272 100644 (file)
--- a/regress/README.regress
+++ b/regress/README.regress
@@ -32,8 +32,12 @@ TEST_SHELL: shell used for running the test scripts.
 
 Individual tests.
 
-You can invoke test-exec.sh directly if you set up the path to find the
-binaries under test and the test scripts themselves, for example:
+You can run an individual test from the top-level Makefile, eg:
+$ make tests LTESTS=agent-timeout
+
+If you need to manipulate the environment more you can invoke test-exec.sh
+directly if you set up the path to find the binaries under test and the
+test scripts themselves, for example:
 
 $ cd regress
 $ PATH=`pwd`/..:$PATH:. TEST_SHELL=/bin/sh sh test-exec.sh `pwd` \