mh-sequence.man: document new '=+' and '=-' for selecting relative msgs

[nmh] / docs / pending-release-notes

diff --git a/docs/pending-release-notes b/docs/pending-release-notes
index a6ae19c593f52672c8840ea25e4b122ef13ed48f..b16b7c1b3deef14547f1132f06b09619a7cfe96e 100644 (file)
--- a/docs/pending-release-notes
+++ b/docs/pending-release-notes
@@ -36,7 +36,26 @@ NEW FEATURES
   if the user does not configure an editor entry in their profile.
 - The format engine (mh_format(5)) now properly accounts for multibyte
   characters when accounting for column widths.
-
+- burst(1) now can burst MIME-formatted digests (messages that contain
+  message/rfc822 parts instead of messages formatted with RFC 934).
+- All proc entries (showproc, moreproc, etc) can now accept entries that
+  contain spaces and shell metacharacters.  If found, such entries will
+  either be space-splitted or processed by /bin/sh.
+- A new program, fmttest(1) is included to help debug format files
+- mhshow/mhstore now have support for RFC-2017 (access-type=url) for
+  external message bodies.
+- Added -retainsequences switch to refile(1).
+- A new program, mhfixmsg(1), is included to rewrite MIME messages with
+  various transformations.
+- Added -[no]rmmproc switches to rmm(1).
+- Added support for Content-Disposition header (RFC 2183) to mhstore(1)
+  and mhn(1) when used with -auto.
+- All nmh commands now support transactional locking for sequence files.
+- There is no longer a per-folder maximum number of sequences.
+- For the SMTP MTA TLS can now be negotiated at the beginning of the
+  connection with the -initialtls switch.
+- Messages can now be selected using a relative offset from some other
+  message, or from the start or end of a sequence.  See mh-sequences(5).
 
 ----------------------------
 OBSOLETE/DEPRECATED FEATURES
@@ -103,3 +122,7 @@ BUG FIXES
 - Removed the artificial limit of 1000 messages at a time for rmmproc.
 - Fixed decoding of header fields when they contain a character that
   can't be converted.
+- post(8) -sasl now honours username in .netrc [Bug #23168].  whom(1),
+  send(1), inc(1), and msgchk(1) also benefit from this fix.  And, nmh
+  now supports specification of any valid filename in place of
+  $HOME/.netrc.