ali: Fix a memory leak spotted by valgrind.

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index eb770fc99653a6914987f62e651a128edb33b335..692f352b14ca3eae8b7e092f8c3c663d0f6049c7 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -21,6 +21,11 @@ commit checklist
 7. update/close bug report (with commit id)?
 8. notify nmh-users?
 
 7. update/close bug report (with commit id)?
 8. notify nmh-users?
 

+A buildbot at http://orthanc.ca:8010/waterfall polls for new commits and
+builds them on a few platforms.  Keep an eye on its progress in case
+you've committed something non-portable.  (If you can provide another
+platform, contact the nmh-workers list.)
+

 
 ---------------------------------
 C library/system call usage notes
 
 ---------------------------------
 C library/system call usage notes


@@ -205,6 +210,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.
 
 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
 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 +240,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:
 
     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
     % 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