From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Cc: Andrew Pinski <pinskia@gmail.com>
Subject: Re: [wwwdocs] Clean up some references to cvs.html
Date: Sat, 29 Dec 2012 17:32:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1212290731520.15650@tuna.site> (raw)
In-Reply-To: <alpine.LNX.2.00.1212271900390.4452@tuna.site>
On Fri, 28 Dec 2012, Gerald Pfeifer wrote:
> Planning to simplify/improve things partly based on that thread,
> I noticed that we actually have too many references to that page,
> so before I proceed with the other changes, this one cleans things
> up a bit (and reduces the number of direct references we have to
> CVS or Subversion).
And here is one for java/. Applied as well.
Gerald
2012-12-29 Gerald Pfeifer <gerald@pfeifer.com>
* gcj2.html: Remove link to our old CVS page.
Index: gcj2.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/gcj2.html,v
retrieving revision 1.9
diff -u -3 -p -r1.9 gcj2.html
--- gcj2.html 25 Mar 2002 20:50:21 -0000 1.9
+++ gcj2.html 29 Dec 2012 17:28:05 -0000
@@ -72,9 +72,9 @@ href="http://gcc.gnu.org/">GCC</a> proje
<h2>How to get it</h2>
<p>The new Java front end is very easy to download and install. Since
-it is it fully integrated into GCC, you can simply follow the <a
-href="http://gcc.gnu.org/cvs.html">GCC download and build
-instructions</a>. Note that you'll want to configure GCC to use the
+it is it fully integrated into GCC, you can simply follow the
+GCC download and build instructions.
+Note that you'll want to configure GCC to use the
appropriate threads system; see <a
href="libgcj2.html">the libgcj page</a> for details.</p>
parent reply other threads:[~2012-12-29 17:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.LNX.2.00.1212271900390.4452@tuna.site>]
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.1212290731520.15650@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
/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).