public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 66483d27c381010c2157da3062e1c65a0860ea2f
Date: Wed,  1 Feb 2023 23:54:28 +0000 (GMT)	[thread overview]
Message-ID: <20230201235428.751FE385842C@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  66483d27c381010c2157da3062e1c65a0860ea2f (commit)
      from  b063df4f4423707a5d1399cde6be05f053b77c59 (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 66483d27c381010c2157da3062e1c65a0860ea2f
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Feb 2 00:54:17 2023 +0100

    readings: Update Nios II reference

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 6e640af1..4bad7e26 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -231,7 +231,7 @@ names.
  
  <li>Nios II
   <br>Manufacturer: Intel (formerly Altera)
-  <br><a href="https://www.intel.com/content/www/us/en/programmable/products/processors/support.html">Nios II Processor Documentation</a>
+  <br><a href="https://www.intel.com/content/www/us/en/support/programmable/support-resources/support-centers/nios-ii-support.html">Nios II Processor Documentation</a>
  </li>
 
  <li>OpenRISC

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

Summary of changes:
 htdocs/readings.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-02-01 23:54 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=20230201235428.751FE385842C@sourceware.org \
    --to=gerald@sourceware.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).