public inbox for
help / color / mirror / Atom feed
From: Gaius Mulley <>
Subject: gcc-wwwdocs branch master updated. 71a814bf75b78649d22936eab3ad6c54f1e2eebf
Date: Thu, 23 Jun 2022 11:15:00 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  71a814bf75b78649d22936eab3ad6c54f1e2eebf (commit)
      from  c402ac6679e0eca4afb99ca5a734ebfed39d0f01 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 71a814bf75b78649d22936eab3ad6c54f1e2eebf
Author: Gaius Mulley <>
Date:   Thu Jun 23 12:11:44 2022 +0100

    Document Git branch devel/m2link.
             * htdocs/git.html: Add description about the
             devel/m2link branch.
    Signed-off-by: Gaius Mulley <>

diff --git a/htdocs/git.html b/htdocs/git.html
index f9acea54..5202363c 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -344,6 +344,18 @@ in Git.</p>
     Patches should be
     prefixed with <code>[modula-2]</code> in the subject line.</dd>
+  <dt>m2link</dt>
+  <dd>This is a short term branch for the
+    <a href="">GNU Modula-2</a>
+    front end to GCC prior to its integration with the mainline.
+    It contains the new scaffold and driver development.  The contents
+    of this branch will be folded back onto the <code>modula-2</code>
+    branch once a significant number of regression tests pass.  It is
+    maintained by
+    <a href="">Gaius Mulley</a>.
+    Patches should be
+    prefixed with <code>[m2link]</code> in the subject line.</dd>
   <dd>This branch is for implementation of a shared memory
     implementation of Fortran coarrays.  It is maintained by


Summary of changes:
 htdocs/git.html | 12 ++++++++++++
 1 file changed, 12 insertions(+)


                 reply	other threads:[~2022-06-23 11:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).