Heads up to anyone tracking branch-1_4 on git. I have just created branch-1.6 which will continue to be the development track towards the next stable release of M4 containing the argv_ref speedups, and will soon be rewinding the branch- 1_4 branch back to v1.4.10 to apply minimal changes and do a release of 1.4.11 that works out of the box on BSD-based systems. My intention is for 1.4.11 to be the end of the 1.4.x branch, and convert all 'stable' development to 1.6.x, leaving all development regarding modules as 2.0 on the master branch.
The following code commits are what I am considering cherry-picking before cutting 1.4.11; plus whatever build machinery patches (independent of code) that make doing a release easier. Speak up if you know of any other issues that should be back-ported from the current state of branch-1.6 that do not involve optimization, or if any of these are too risky for a quick release. Minor security fix: Quote output of mkstemp. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=bd9900d Security fix: avoid arbitrary code execution with 'm4 -F'. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=031a71a Never let printf failures go undetected. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=ab8d0f0 Fix 'm4 -F file -t undefined'. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=75160ba POSIX requires defn(`a',`b') to concatenate definitions. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=154c86a Fix regression on NetBSD from 2007-05-28. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=c1841dc -- Eric Blake _______________________________________________ M4-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/m4-patches
