Eric, Sorry about the scrambled patch files. I am re-sending as text only (still mime encoded) with both the branch-1.4 and branch-1.6 patch files sent as gzipped attachments. This should force the attachments to be encoded using base64 and arrive intact.
David On 5/22/25 10:54, Eric Blake wrote:
On Tue, May 20, 2025 at 02:31:04PM -0400, David M. Warme wrote:Eric, I have incorporated most of the changes that you have identified. This patch is from very recent branch-1.4.Thanks for re-working this! I'm still reluctant to merge this into branch-1.4 (which is supposed to be for bug-fixes only), but my plan is to take your version for branch-1.6 and apply it this weekend if I can. At that point, I probably need to cut an alpha release (I think the next version number is v1.5.89) so all the current code in branch-1.6 will be more formal than just a git release, even though there's still lots to do before I feel comfortable releasing 1.6 proper (among others, I still need to resolve the emacs/BRE/ERE regex flavor issue in a way that can be probed at runtime without spurious warnings).7cbad39e..99952f14 100644 --- a/doc/m4.texi +++ b/doc/m4.texi @@ -36,6 +36,14 @@ @r{[}@var{\varname\} = @samp{\default\}@r{]} @end macro +@c @auxresult{auxfile} +@c ------------ +@c Used in examples to indicate outputFor whatever reason, your message was sent in mime/multipart with both text and html versions. I read my email in text (on purpose), and that renders your patch extremely broken. Having to scrape your patch out of html is hard, but probably doable, so I'll attempt it this time. But in the future, please send patches as plain-text only (possibly as attachments, if you can't figure out how to make your mailer do it nicely in the body), so that they don't get corrupted like this.
m4-1.4-makedep.patch.gz
Description: application/gzip
m4-1.6-makedep.patch.gz
Description: application/gzip
_______________________________________________ M4-patches mailing list [email protected] https://lists.gnu.org/mailman/listinfo/m4-patches
