public inbox for
help / color / mirror / Atom feed
From: Jonathan Wakely <>
Subject: gcc-wwwdocs branch master updated. 996afe17497b8c06f00c763bcf7fe2b971bb0f05
Date: Tue,  1 Feb 2022 12:56:12 +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  996afe17497b8c06f00c763bcf7fe2b971bb0f05 (commit)
      from  5f199e1197b67b4304a3be54579c2141c39bff30 (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 996afe17497b8c06f00c763bcf7fe2b971bb0f05
Author: Jonathan Wakely <>
Date:   Tue Feb 1 12:56:07 2022 +0000

    Uncomment header for Fortran issues

diff --git a/htdocs/gcc-12/porting_to.html b/htdocs/gcc-12/porting_to.html
index 7f4a2936..470703c7 100644
--- a/htdocs/gcc-12/porting_to.html
+++ b/htdocs/gcc-12/porting_to.html
@@ -99,9 +99,8 @@ base classes can often be completely removed, or the typedefs for
 <h2 id="fortran">Fortran language issues</h2>
 <h3 id="co_reduce_operation">Argument name for CO_REDUCE</h3>


Summary of changes:
 htdocs/gcc-12/porting_to.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)


                 reply	other threads:[~2022-02-01 12:56 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).