public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Simplify gcc-6/porting_to.html and gcc-7/porting_to.html
Date: Sun, 23 Sep 2018 10:55:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.21.1809231238140.3785@anthias.pfeifer.com> (raw)

After the change I made to gcc-8/porting_to.html yesterday, I now
also looked into its older brethren and made the following changes,
also removing empty sections.

Committed.

Gerald

Index: gcc-6/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/porting_to.html,v
retrieving revision 1.27
diff -u -r1.27 porting_to.html
--- gcc-6/porting_to.html	1 Sep 2018 23:42:06 -0000	1.27
+++ gcc-6/porting_to.html	23 Sep 2018 10:38:10 -0000
@@ -27,12 +27,6 @@
 </p>
 
 
-<h2 id="cpp">Preprocessor issues</h2>
-
-
-<h2 id="c">C language issues</h2>
-
-
 <h2 id="cxx">C++ language issues</h2>
 
 <h3 id="gxx14">Default standard is now GNU++14</h3>
Index: gcc-7/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/porting_to.html,v
retrieving revision 1.16
diff -u -r1.16 porting_to.html
--- gcc-7/porting_to.html	1 Sep 2018 23:42:06 -0000	1.16
+++ gcc-7/porting_to.html	23 Sep 2018 10:38:10 -0000
@@ -26,12 +26,6 @@
 </p>
 
 
-<h2 id="cpp">Preprocessor issues</h2>
-
-
-<h2 id="c">C language issues</h2>
-
-
 <h2 id="cxx">C++ language issues</h2>
 
 <h3 id="hypothetical-instantiation">Stricter rules when using templates</h3>

                 reply	other threads:[~2018-09-23 10:41 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:
  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=alpine.LSU.2.21.1809231238140.3785@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@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).