> On 24 Dec 2022, at 03:56, Mike Fulton <[email protected]> wrote: > > Hello,
Hi Mike, > I am new to the m4 community and would like to understand the best way to > propose a patch. > I have a few small changes I would like to request – one minor one where > there is a macro collision on z/OS where __stat is already defined, and two > others where I would like to add some z/OS specific code for conversion to > ASCII from EBCDIC. > I have a third where the error message from our runtime is ‘<message number> > No such file or directory’ instead of just ‘No such file or directory’. > What is the preferred way to propose these changes for the community? https://git.savannah.gnu.org/cgit/m4.git/tree/HACKING?h=branch-1.4 almost covers it but not quite. I would follow the guidance in that file wrt style and such, and then send patches to the m4-patches mailing list ([email protected] <mailto:[email protected]>) using git-send-email. Best, sam
signature.asc
Description: Message signed with OpenPGP
