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. 87d3099c9490efd449f2c23ff886dd1117cdc578 Date: Tue, 1 Nov 2022 09:48:43 +0000 (GMT) [thread overview] Message-ID: <20221101094844.E0195385840E@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 87d3099c9490efd449f2c23ff886dd1117cdc578 (commit) from 3d248f971092a43effc4b44e3cf9113bac6f4a5a (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 87d3099c9490efd449f2c23ff886dd1117cdc578 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Nov 1 10:48:24 2022 +0100 codingconventions: Move two links to https diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index f88ef019..f5e22983 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -737,7 +737,7 @@ the latest version is at before going into GCC.</li> <li>fastjar: The master sources were at <a -href="http://fastjar.sourceforge.net/">fastjar.sourceforge.net</a>. +href="https://fastjar.sourceforge.net/">fastjar.sourceforge.net</a>. However, the upstream source seems to be dead, so fastjar is essentially maintained in the GCC source tree.</li> @@ -764,7 +764,7 @@ FSF website, or are autogenerated. These files should not be changed without prior permission, if at all.</li> <li>libgcc/config/libbid: The master sources come from Intel BID library -<a href="http://www.netlib.org/misc/intel/">Intel BID library</a>. +<a href="https://www.netlib.org/misc/intel/">Intel BID library</a>. Bugs should be reported to <a href="mailto:marius.cornea@intel.com">marius.cornea@intel.com</a> and ----------------------------------------------------------------------- Summary of changes: htdocs/codingconventions.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-11-01 9:48 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=20221101094844.E0195385840E@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).