Make sure we retry if possible upon a TLS read, and give a more meaningful

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index eb770fc99653a6914987f62e651a128edb33b335..f0f05c8250158726ae4656cbb612d401cae93aa6 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -205,6 +205,10 @@ In the nmh test suite, nmh programs to be tested should be invoked
 through the run_test or run_prog shell functions defined in
 test/common.sh.
 
+Instead of echoing test progress, use start_test()/finish_test()
+from tests/common.sh.  These will report the particular test name,
+within the test, only if there is a failure.
+
 To enable the use of valgrind, where available, set the environment
 variable NMH_VALGRIND to a non-null value.  However, a separate
 environment variable, VALGRIND_ME, triggers the use of valgrind in
@@ -231,7 +235,7 @@ here; the convention for release candidates is to use something like
 
     Note you are still on the master branch at this point.  Mark the
     current revision as the branchpoint for the new release branch:
-    
+
     % git tag -a -m "This tag marks the point where we started the branch for 1.5" 1.5-branchpoint
 
     Now mark the master branch with a post-release version number (the