Document changes to mhbuild and send.

[nmh] / docs / pending-release-notes

diff --git a/docs/pending-release-notes b/docs/pending-release-notes
index b4d3e63114f696672686acb451ba23385735fd1c..8c1de2bf831409a120a76d24f0dadd3502fe8eda 100644 (file)
--- a/docs/pending-release-notes
+++ b/docs/pending-release-notes
@@ -61,9 +61,17 @@ NEW FEATURES
 - mhbuild(1) can now encode 8-bit message headers using RFC-2047 encoding
   rules.
 - The whatnow(1) attach feature will determine the content type of an
 - mhbuild(1) can now encode 8-bit message headers using RFC-2047 encoding
   rules.
 - The whatnow(1) attach feature will determine the content type of an

-  attachment using a program such as file --mime, if available at
+  attachment using a program such as file --mime-type, if available at

   configuration time.  If not, it will use mhshow-suffix- entries as
   configuration time.  If not, it will use mhshow-suffix- entries as

-  before.
+  before.  The -v switch to attach causes it to display the mhbuild
+  directive that send(1) will use.
+- mhbuild(1) now supports the -auto/-noauto flags (to be used by send(1)
+  when invoking mhbuild automatically).
+- mhbuild(1) now is automatically run by send, to insure that all outgoing
+  messages have proper MIME formatting.
+- A new header, "Attach", is supported by mhbuild; it is used to replace
+  previous functionality (which by default used a header named
+  Nmh-Attachment).

 
 -----------------
 OBSOLETE FEATURES
 
 -----------------
 OBSOLETE FEATURES