exmh 2.9.0 has escaped....
[email protected] Wed, 07 Nov 2018 01:15:14 -0500
| Newsgroups | gmane.mail.exmh.devel,gmane.mail.exmh.user |
|---|---|
| Message-ID | <[email protected]> |
--===============0771517633911700394== Content-Type: multipart/signed; boundary="==_Exmh_1541571314_22451P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit --==_Exmh_1541571314_22451P Content-Type: text/plain; charset=us-ascii I tagged 2.9.0 and pushed it to the git repository and 2.9.0 tarballs to the sourceforge project page. I *think* I caught most of the important 2.8.0-> 2.9.0 references. If I missed anything, yell... In related questions: Is it going to cause any issues if I make nmh 1.6 the minimum supported underlying MH release? I'm looking at taking a baseball bat to our current multipart composition support, but it would leverage mhbuild which first appeared in nmh 1.6. --==_Exmh_1541571314_22451P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Comment: Exmh version 2.9.0 11/07/2018 iQEVAwUBW+KC8Y0DS38y7CIcAQKW3ggAk/G3wKu4BEQ0+qjG+wWV1jFeF5CN0dTi 4a6ZcgmrwlHWUltc5dvkpzSNQg+rZfQ3YeWISLVTavoQ+RpXCF+kIe2OSPGD9p3y 83U+86lwVhXj5wKyLvGOi9h6NWTeQ3Xan8J+SgogosdREBfHMBbXWJnBqVsARtbH e8+lClzo4IBESt06U6p1hxLOM57AHD0Q4l7wnLPp1RIVxER6fxo/aWs1wPpS1Z6j uR8MV9u5m/UHfNz7a3l86A7k1HxWjM07yJZVKFoLS8n2r/VazgRkca+VZDKvVxSH NWag344s+CLqToUINSIo3i3bTK3E+Dm5hwH3QirhV/iQ2BK7s8Lepg== =/Yy5 -----END PGP SIGNATURE----- --==_Exmh_1541571314_22451P-- --===============0771517633911700394== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Exmh-workers mailing list [email protected] https://www.redhat.com/mailman/listinfo/exmh-workers --===============0771517633911700394==--