From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [wwwdocs,Java] /java -- sourceware.org now defaults to https
Date: Sat, 28 May 2016 13:09:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1605281507290.2874@anthias.pfeifer.com> (raw)
Commmitted.
2016-05-28 Gerald Pfeifer <gerald@pfeifer.com>
* done.html: Convert sourceware.org links to https.
* index.html: Ditto.
* news.html: Ditto.
Index: done.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/done.html,v
retrieving revision 1.54
diff -u -r1.54 done.html
--- done.html 27 Jun 2015 21:51:17 -0000 1.54
+++ done.html 28 May 2016 13:06:34 -0000
@@ -162,7 +162,7 @@
<!-- End Fluid Dynamics -->
<!-- rhug -->
<tr valign="top">
- <td><b><a href="http://sourceware.org/rhug/">rhug</a></b></td>
+ <td><b><a href="https://sourceware.org/rhug/">rhug</a></b></td>
<td>Anthony Green and friends have set up rhug, a collection
of free software Java packages set up to build with gcj.
Both sources and RPMs are available.
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/index.html,v
retrieving revision 1.178
diff -u -r1.178 index.html
--- index.html 9 Apr 2016 16:25:57 -0000 1.178
+++ index.html 28 May 2016 13:06:34 -0000
@@ -115,7 +115,7 @@
on <a href="http://freecode.com/projects/libjit">libjit</a> and <a
href="http://llvm.org/">LLVM</a> respectively. The source code for these
JITs is available via the "gcj-jit" module of the <a
-href="http://sourceware.org/rhug/">rhug</a> repository.
+href="https://sourceware.org/rhug/">rhug</a> repository.
</dd>
<dt>April 4, 2006</dt>
Index: news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/news.html,v
retrieving revision 1.19
diff -u -r1.19 news.html
--- news.html 6 Jul 2014 00:16:47 -0000 1.19
+++ news.html 28 May 2016 13:06:34 -0000
@@ -152,7 +152,7 @@
<dd>
Gary Benson from Red Hat has released
<a href="http://people.redhat.com/gbenson/naoko/">Naoko</a>: a subset
-of the <a href="http://sourceware.org/rhug/">rhug</a> packages
+of the <a href="https://sourceware.org/rhug/">rhug</a> packages
that have been repackaged for eventual inclusion in Red Hat Linux.
Naoko basically comprises binary RPMS of Ant, Tomcat, and their
dependencies built with gcj.
@@ -171,7 +171,7 @@
of <a href="http://www.eclipse.org/">Eclipse</a>, a free software IDE
written in Java, that has been compiled with a modified gcj.
You can find more information
-<a href="http://sourceware.org/eclipse/">here</a>. We'll be
+<a href="https://sourceware.org/eclipse/">here</a>. We'll be
integrating the required gcj patches in the near future.
</dd>
@@ -425,7 +425,7 @@
<dt>February 8, 2001</dt>
<dd>
Made use of Warren Levy's change to the
-<a href="http://sourceware.org/mauve/">Mauve test suite</a> to handle
+<a href="https://sourceware.org/mauve/">Mauve test suite</a> to handle
regressions.
Modifications have been made to <tt>mauve.exp</tt> to copy the newly created
<tt>xfails</tt> file of known library failures from the source tree
reply other threads:[~2016-05-28 13:09 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=alpine.LSU.2.20.1605281507290.2874@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-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).