Re: m4 patch requests

--Apple-Mail=_2DFCCF5F-948D-4215-9995-71037E980977
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 24 Dec 2022, at 03:56, Mike Fulton <[email protected]> wrote:
>=20
> 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 =E2=80=93 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 =E2=80=98<mes=
sage number> No such file or directory=E2=80=99 instead of just =E2=80=98N=
o such file or directory=E2=80=99.
>  What is the preferred way to propose these changes for the community?

https://git.savannah.gnu.org/cgit/m4.git/tree/HACKING?h=3Dbranch-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

--Apple-Mail=_2DFCCF5F-948D-4215-9995-71037E980977
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iNUEARYKAH0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCY6aDa18UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB
NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MAAKCRBzhAn1IN+R
kKVbAQCZzkq5X33BZ1MlNqw8ubfLLHdFZ1YntuUkpfpyjIS6CAEAqwCzRDj/c8MO
rxL6SnzaOow9McqeDHmOrcRXKQBKkgA=
=lOyP
-----END PGP SIGNATURE-----

--Apple-Mail=_2DFCCF5F-948D-4215-9995-71037E980977--