public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: pinskia@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 330078ceda3f17bf6136f45ba5b4aa706042f516
Date: Wed, 05 Feb 2020 10:43:00 -0000	[thread overview]
Message-ID: <20200205104354.34140.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  330078ceda3f17bf6136f45ba5b4aa706042f516 (commit)
      from  26f4802d2ffd7aa182e559414638b6c546054f64 (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 330078ceda3f17bf6136f45ba5b4aa706042f516
Author: Andrew Pinski <apinski@marvell.com>
Date:   Wed Feb 5 10:41:09 2020 +0000

    Add link to porting_to.html from the changes page for GCC 9
    
    Looks like the porting_to page was not linked to the changes
    page for GCC 9. So uncomments it out.

diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html
index c0e581f..22b069c 100644
--- a/htdocs/gcc-9/changes.html
+++ b/htdocs/gcc-9/changes.html
@@ -17,11 +17,9 @@
 <p>
 This page is a "brief" summary of some of the huge number of improvements
 in GCC 9.
-<!--
 You may also want to check out our
 <a href="porting_to.html">Porting to GCC 9</a> page and the
 <a href="../onlinedocs/index.html#current">full GCC documentation</a>.
--->
 </p>
 
 <!-- .................................................................. -->

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

Summary of changes:
 htdocs/gcc-9/changes.html | 2 --
 1 file changed, 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-02-05 10:43 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=20200205104354.34140.qmail@sourceware.org \
    --to=pinskia@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).