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] Various tweaks to java/build-snapshot.html
Date: Sat, 29 Oct 2011 19:39:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1110292135080.3250@gerinyyl.fvgr> (raw)

2011-10-29  Gerald Pfeifer  <gerald@pfeifer.com>
 
	* build-snapshot.html: Adjust title to not refer to CVS any more.
	Adjust formatting of title.
	Change link from CVS instructions to SVN.

Installed.

Gerald

Index: build-snapshot.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/build-snapshot.html,v
retrieving revision 1.16
diff -u -r1.16 build-snapshot.html
--- build-snapshot.html	29 Jul 2002 16:50:01 -0000	1.16
+++ build-snapshot.html	29 Oct 2011 19:33:54 -0000
@@ -1,23 +1,18 @@
 <html>
 
 <head>
-<title>How to build GCJ/LIBGCJ from snapshots or cvs</title>
+<title>How to build GCJ/LIBGCJ from snapshots or checkouts</title>
 </head>
 
 <body>
 
-<table border="0" cellpadding="4" width="95%">
-        <tr bgcolor="#b0d0ff"> 
-          <th align="center"> 
-            <h2>Howto build and run libgcj/gcj snapshots or cvs</h2>
-          </th>
-        </tr>
-
+<h1>Howto build and run libgcj/gcj snapshots or checkouts</h1>
 
+<table border="0" cellpadding="4" width="95%">
 <tr bgcolor="#cccccc">
 <td>
 <pre>
-1. <a href="../snapshots.html">Get a GCC snapshot</a> or <a href="../cvs.html">obtain GCC via CVS</a>.
+1. <a href="../snapshots.html">Get a GCC snapshot</a> or <a href="../svn.html">check out the sources</a>.
 </pre>
 </td>
 </tr>

                 reply	other threads:[~2011-10-29 19:39 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.LNX.2.00.1110292135080.3250@gerinyyl.fvgr \
    --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).