Use Nmh-Attach for attach header field name, and accept Attach.

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index 5ab014abfe869979500d6fee9a14d3811f85eac8..eb770fc99653a6914987f62e651a128edb33b335 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -111,9 +111,16 @@ sbr/
     file.  These functions are of general use and are called from throughout
     nmh.
 
     file.  These functions are of general use and are called from throughout
     nmh.
 

+SPECS/
+    Contains files such as RPM specs.
+

 test/
     The num unit test suite.
 
 test/
     The num unit test suite.
 

+tools/
+    "tools" contains tools, scripts, and supporting files used by the
+    developers while writing, debugging, and testing the code.
+

 uip/
     "uip" stands for "User Interface Programs".  Most nmh commands have a file
     in this directory named <command>.c containing the code for that command
 uip/
     "uip" stands for "User Interface Programs".  Most nmh commands have a file
     in this directory named <command>.c containing the code for that command


@@ -156,6 +163,7 @@ to any new branches that you create:
 
     % git config branch.autosetuprebase always
 
 
     % git config branch.autosetuprebase always
 

+

 -------------------------------------------------------
 nmh-local functions to use in preference to OS versions
 -------------------------------------------------------
 -------------------------------------------------------
 nmh-local functions to use in preference to OS versions
 -------------------------------------------------------


@@ -193,15 +201,20 @@ nmh test suite
 The nmh test suite is run through the Makefile, with "make check"
 or "make distcheck".
 
 The nmh test suite is run through the Makefile, with "make check"
 or "make distcheck".
 

+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.
+

 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
 test/inc/test-eom-align because it greatly extends the duration of
 that test.
 
 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
 test/inc/test-eom-align because it greatly extends the duration of
 that test.
 

-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.
+If valgrind complains about "serious error when reading debuginfo"
+from a library, either update or remove the debuginfo package for
+the offending library.
+

 
 -------------
 releasing nmh
 
 -------------
 releasing nmh


@@ -225,7 +238,9 @@ here; the convention for release candidates is to use something like
     convention here is to use VERSION+dev as the version number).
 
     % echo 1.5+dev > VERSION
     convention here is to use VERSION+dev as the version number).
 
     % echo 1.5+dev > VERSION

-    % git commit VERSION; git push --tags
+    % git commit VERSION
+    % git push
+    % git push --tags

 
     Then do:
 
 
     Then do:
 


@@ -237,7 +252,7 @@ here; the convention for release candidates is to use something like
     % date +"%e %B %Y" > DATE
     (DATE should contain something like "30 December 2000")
 
     % date +"%e %B %Y" > DATE
     (DATE should contain something like "30 December 2000")
 

- 3. % git commit VERSION DATE
+ 3. % git commit VERSION DATE; git push

 
  4. % git tag -a 1.5 -m 'Releasing nmh-1.5.'
     % git push --tags
 
  4. % git tag -a 1.5 -m 'Releasing nmh-1.5.'
     % git push --tags