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] Merge java/.htaccess into top level .htaccess and convert to https
Date: Tue, 01 Jul 2014 12:12:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1407011315250.30120@tuna.site> (raw)
2014-07-01 Gerald Pfeifer <gerald@pfeifer.com>
* .htaccess: Merge java/.htaccess into top level .htaccess
and convert to https.
Committed.
Index: java/.htaccess
===================================================================
RCS file: java/.htaccess
diff -N java/.htaccess
--- java/.htaccess 4 May 2001 16:24:26 -0000 1.6
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,4 +0,0 @@
-Redirect permanent /java/FAQ.html http://gcc.gnu.org/java/faq.html
-Redirect permanent /java/gcj.html http://gcc.gnu.org/java/index.html
-Redirect permanent /java/libgcj.html http://gcc.gnu.org/java/index.html
-Redirect permanent /java/about.html http://gcc.gnu.org/about.html
Index: .htaccess
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/.htaccess,v
retrieving revision 1.32
diff -u -r1.32 .htaccess
--- .htaccess 11 Jun 2014 17:45:32 -0000 1.32
+++ .htaccess 1 Jul 2014 11:15:26 -0000
@@ -42,6 +42,11 @@
Redirect permanent /onlinedocs/g77_bugs.html https://gcc.gnu.org/onlinedocs/g77/Trouble.html
Redirect permanent /onlinedocs/g77/ https://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/
+Redirect permanent /java/FAQ.html https://gcc.gnu.org/java/faq.html
+Redirect permanent /java/gcj.html https://gcc.gnu.org/java/
+Redirect permanent /java/libgcj.html https://gcc.gnu.org/java/
+Redirect permanent /java/about.html https://gcc.gnu.org/about.html
+
Redirect permanent /bugs.html https://gcc.gnu.org/bugs/
Redirect permanent /c9xstatus.html https://gcc.gnu.org/c99status.html
Redirect permanent /cvswrite.html https://gcc.gnu.org/svnwrite.html
reply other threads:[~2014-07-01 12:12 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.1407011315250.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).