public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [wwwdocs,Java] Replace sources.redhat.com by sourceware.org
Date: Sun, 21 Oct 2012 02:05:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1210210402530.2076@tuna.site> (raw)

...and some other simplifications and improvements I noticed on
the way.

This was triggered by a note that the sources.redhat.com DNS entry
is going to go away at some point in the future that I got yesterday.

Applied.

Gerald


2012-10-21  Gerald Pfeifer  <gerald@pfeifer.com>

	* news.html: Replace references to sources.redhat.com by
	sourceware.org.
	Avoid a reference to CVS.
	Some style adjustments to the February 8, 2001 entry.

Index: news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/news.html,v
retrieving revision 1.12
diff -u -3 -p -r1.12 news.html
--- news.html	19 Sep 2010 20:35:03 -0000	1.12
+++ news.html	21 Oct 2012 02:02:51 -0000
@@ -153,7 +153,7 @@ code size heuristics.  It is enabled by 
 <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://sources.redhat.com/rhug/">rhug</a> packages 
+of the <a href="http://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.
@@ -172,8 +172,8 @@ A team of hackers from Red Hat has relea
 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://sources.redhat.com/eclipse/">here</a>.  We'll be
-integrating the required gcj patches into cvs in the near future.
+<a href="http://sourceware.org/eclipse/">here</a>.  We'll be
+integrating the required gcj patches in the near future.
 </dd>
 
 <dt>July 31, 2003</dt>
@@ -426,7 +426,7 @@ find bugs!
 <dt>February 8, 2001</dt>
 <dd>
 Made use of Warren Levy's change to the
-<a href="http://sources.redhat.com/mauve/">Mauve test suite</a> to handle
+<a href="http://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
@@ -434,9 +434,9 @@ to the directory where the libjava <tt>'
 This allows the testsuite to ignore <tt>XFAIL</tt>s and thus highlight
 true regressions in the library.  The Mauve tests are
 automatically run as part of a libjava
-<tt>'make check'</tt> as long as the Mauve suite is accessible
-and the env var <tt>MAUVEDIR</tt> is set to point to the top-level
-of the <a href="http://sources.redhat.com/mauve/download.html">Mauve source</a>.
+<code>make check</code> as long as the Mauve suite is accessible and the
+environment variable <code>MAUVEDIR</code> is set to point to the top-level
+of the Mauve sources.
 </dd>
 
 <dt>January 28, 2001</dt>

             reply	other threads:[~2012-10-21  2:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-21  2:05 Gerald Pfeifer [this message]
2012-10-23  9:47 ` Andrew Hughes
2012-10-23  9:53   ` Andrew Haley
2012-10-23 11:14     ` Mark Wielaard

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.LNX.2.00.1210210402530.2076@tuna.site \
    --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).