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. 68c7403bff82ca52fa9efcee7b041339715e1274
Date: Sun, 30 May 2021 22:19:49 +0000 (GMT) [thread overview]
Message-ID: <20210530221949.BAA563858018@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 68c7403bff82ca52fa9efcee7b041339715e1274 (commit)
from 47b1f39c5e4a31073311c48a51872ccf7bd51659 (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 68c7403bff82ca52fa9efcee7b041339715e1274
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Mon May 31 00:17:25 2021 +0200
readings: Remove PRU-ICSS documentation reference
TI's server has been telling us that "The PRU-ICSS wiki is in the
process of being migrated to software-dl.ti.com" for five months.
Time to pull the plug.
diff --git a/htdocs/readings.html b/htdocs/readings.html
index c4c0618a..33ed5822 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -256,7 +256,6 @@ names.
<li>pru
<br />Manufacturer: Texas Instruments
- <br /><a href="https://processors.wiki.ti.com/index.php/PRU-ICSS">Official PRU Documentation</a>
<br /><a href="https://elinux.org/Category:PRU">Community PRU Documentation</a>
</li>
-----------------------------------------------------------------------
Summary of changes:
htdocs/readings.html | 1 -
1 file changed, 1 deletion(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2021-05-30 22:19 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=20210530221949.BAA563858018@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).