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. 5b65d13253d7067b581b4886d0d4a3f5f454c1f3 Date: Thu, 10 Nov 2022 09:42:15 +0000 (GMT) [thread overview] Message-ID: <20221110094215.B4E333836644@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 5b65d13253d7067b581b4886d0d4a3f5f454c1f3 (commit) from bb0012176fc7ae9f2528a802a17b97be0bb776ae (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 5b65d13253d7067b581b4886d0d4a3f5f454c1f3 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Nov 10 10:40:55 2022 +0100 readings: Remove linux-c6x.org linux-c6x.org has been dead for at two-and-a-half months and a web search did not reveal a good alternate site. diff --git a/htdocs/readings.html b/htdocs/readings.html index df89bc9c..5e3db8c2 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -105,7 +105,6 @@ names. <li>C6X <br>Manufacturer: Texas Instruments <br>Exact chip name: TMS320C6X - <br><a href="http://linux-c6x.org/">Site for the Linux on C6X project</a> </li> <li>CR16 ----------------------------------------------------------------------- Summary of changes: htdocs/readings.html | 1 - 1 file changed, 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-11-10 9:42 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=20221110094215.B4E333836644@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: linkBe 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).