From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Cc: Tobias Burnus <burnus@net-b.de>
Subject: [wwwdocs,Java] Make links in faq.html and java/faq.html relative
Date: Sun, 29 Jun 2014 20:14:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1406292133130.30120@tuna.site> (raw)
Ever since
2007-10-01 Gerald Pfeifer <gerald@pfeifer.com>
* gcc_release: Do not include copies of faq.html in releases,
and remove all the explicit support code to pull in web pages.
there was no reason faq.html (formerly included as FAQ) needed absolute
links unless wrt. services only available on gcc.gnu.org. This adjusts
both faq.html and java/faq.html accordingly.
As a nice side effect, this avoids http vs https changes.
Applied.
Gerald
Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.219
diff -u -r1.219 faq.html
--- faq.html 28 Jun 2014 11:59:42 -0000 1.219
+++ faq.html 29 Jun 2014 19:38:24 -0000
@@ -8,9 +8,6 @@
<h1>GCC Frequently Asked Questions</h1>
-<p>The latest version of this document is always available at
-<a href="http://gcc.gnu.org/faq.html">http://gcc.gnu.org/faq.html</a>.</p>
-
<p>This FAQ tries to answer specific questions concerning GCC. For
general information regarding C, C++, resp. Fortran please check the
<a href="http://c-faq.com/">comp.lang.c FAQ</a>,
@@ -21,7 +18,7 @@
<p>Other GCC-related FAQs:
<a href="https://gcc.gnu.org/onlinedocs/libstdc++/faq.html">
libstdc++-v3</a>, and
- <a href="http://gcc.gnu.org/java/faq.html">GCJ</a>.</p>
+ <a href="java/faq.html">GCJ</a>.</p>
<hr />
<h1>Questions</h1>
@@ -105,7 +102,7 @@
These are included in the sources for a release in INSTALL/specific.html,
and the <a href="https://gcc.gnu.org/install/specific.html">latest version</a>
is always available at the GCC web site.
-Reports of <a href="http://gcc.gnu.org/buildstat.html">successful builds</a>
+Reports of <a href="buildstat.html">successful builds</a>
for several versions of GCC are also available at the web site.</p>
<hr />
2014-06-29 Gerald Pfeifer <gerald@pfeifer.com>
* faq.html: Remove two absolute links/references.
Index: java/faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/faq.html,v
retrieving revision 1.73
diff -u -r1.73 faq.html
--- java/faq.html 28 Jun 2014 17:12:51 -0000 1.73
+++ java/faq.html 29 Jun 2014 19:38:26 -0000
@@ -6,7 +6,7 @@
<body>
<h1>The GCJ FAQ</h1>
- <p>The latest version of this document is always available at <a href="faq.html">http://gcc.gnu.org/java/faq.html</a>.</p>
+
<ol>
<li><a href="#1_0">General Questions</a>
<ol>
@@ -422,7 +422,8 @@
used for CNI with the -fno-rtti option.
This constraint does not apply in version 3.0 and later.</p>
- <p>The primary source of documentation for CNI is at <a href="papers/cni/t1.html">http://gcc.gnu.org/java/papers/cni/t1.html</a></p>
+ <p>The primary source of documentation for CNI is
+ <a href="papers/cni/t1.html">this paper</a>.</p>
</dd>
</dl>
reply other threads:[~2014-06-29 20:14 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.11.1406292133130.30120@tuna.site \
--to=gerald@pfeifer.com \
--cc=burnus@net-b.de \
--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).