Hi Ken, I thought a deprecating a part of nmh meant add the warning it was for the axe in release N and axing it in release M where M>N. But commit 43d9833b, http://git.savannah.nongnu.org/cgit/nmh.git/commit/?id=43d9833bf1dcf38c7892a23951bf1d968028a15e adds this to docs/pending-release-notes:
- The generation and verification of Content-MD5 headers is no longer performed. The -check and -nocheck switches to various nmh programs that would control this functionality still exist, but are non-functional and will be removed in the next release. That's axing the feature without deprecation and trying to hoodwink the user that it hasn't happened. :-( Either it should be deprecated, or axed in a release without forewarning. And if the latter then is that agreement we can do it for other things too? After all, many users don't read the release notes and thus miss the deprecation warnings, or they upgrade several of our releases in one bound due to their distro, etc., striding differently, so a feature is effectively axed for them without warning anyway. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers