public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-3.4: Switch www.eclipse.org to https
Date: Sun, 15 Jan 2023 23:16:52 +0100 (CET)	[thread overview]
Message-ID: <20230115221707.EFEEC33E24@hamza.pair.com> (raw)


---
 htdocs/gcc-3.4/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/gcc-3.4/changes.html b/htdocs/gcc-3.4/changes.html
index aac9a245..d9985673 100644
--- a/htdocs/gcc-3.4/changes.html
+++ b/htdocs/gcc-3.4/changes.html
@@ -738,7 +738,7 @@ and not your code, that is broken.</em></p>
       href="http://www.gnu.org/software/classpath/">GNU Classpath</a>.</li>
     <li>Class loading is now much more correct; in particular the
       caller's class loader is now used when that is required.</li>
-    <li><a href="http://www.eclipse.org/">Eclipse 2.x</a> will run
+    <li><a href="https://www.eclipse.org">Eclipse 2.x</a> will run
       out of the box using <code>gij</code>.</li>
     <li>Parts of <code>java.nio</code> have been implemented.
       Direct and indirect buffers work, as do fundamental file and
-- 
2.38.1

                 reply	other threads:[~2023-01-15 22:17 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=20230115221707.EFEEC33E24@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@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).