From: Gaius Mulley <gaiusmod2@gmail.com>
To: gcc@gcc.gnu.org, dje.gcc@gmail.com
Subject: Proposal for the merger of devel/modula-2 into master
Date: Fri, 13 May 2022 23:56:11 +0100 [thread overview]
Message-ID: <87wneprqic.fsf@debian> (raw)
Hi David,
David Edelsohn <dje.gcc@gmail.com> writes:
> I hope that you and the GNU Modula-2 team can propose the merge of the
> Modula-2 front-end and library soon.
[reposting with a new title for mailing list clarity]
Yes I was also wondering whether now might be a sensible time for the
Modula-2 front end to move across onto the master branch?
The current Modula-2 front end and libraries are in the branch:
devel/modula-2 and it builds on gnu/linux/amd64, gnu/linux/aarch64,
gnu/linux/sparc64, solaris/sparc64, gnu/linux/i386, gnu/linux/ppc64le,
gnu/linux/power7 (and probably others). (Test results posted to
gcc-testresults).
More than happy for the gm2 front end to be merged and/or help or
receive instructions on how to progress the merge
regards,
Gaius
next reply other threads:[~2022-05-13 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 22:56 Gaius Mulley [this message]
2022-05-14 6:15 ` Richard Biener
2022-05-14 12:06 ` Gaius Mulley
2022-05-18 13:47 ` Proposal for the merger and patch set Gaius Mulley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wneprqic.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).