public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: burnus@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 8655ef3f64b77655417d97079348c13ab1a87c8d
Date: Tue, 03 Dec 2019 08:44:00 -0000	[thread overview]
Message-ID: <20191203084417.116603.qmail@sourceware.org> (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  8655ef3f64b77655417d97079348c13ab1a87c8d (commit)
      from  2e5b610bc77329bb2e1fdd3dff1efcd08b99b830 (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 8655ef3f64b77655417d97079348c13ab1a87c8d
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Tue Dec 3 09:43:17 2019 +0100

    GCC 10 porting to - comment empty block
    
    	* htdocs/gcc-10/porting_to.html: Comment <h2>Link</h2>.

diff --git a/htdocs/gcc-10/porting_to.html b/htdocs/gcc-10/porting_to.html
index 2c40419..5e569c2 100644
--- a/htdocs/gcc-10/porting_to.html
+++ b/htdocs/gcc-10/porting_to.html
@@ -128,7 +128,9 @@ longer compile it.)
 <h2 id="cxx">C++ language issues</h2>
 -->
 
+<!--
 <h2 id="links">Links</h2>
+-->
 
 </body>
 </html>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/porting_to.html |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2019-12-03  8:44 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=20191203084417.116603.qmail@sourceware.org \
    --to=burnus@gcc.gnu.org \
    --cc=gcc-cvs-wwwdocs@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).