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
Cc: java-patches@gcc.gnu.org
Subject: [wwwdocs] Move the generic redirect for /java/ past all more specific ones
Date: Thu, 29 Dec 2016 22:33:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1612291802330.2994@anthias.pfeifer.com> (raw)

Move the generic redirect for /java/ past all more specific ones for
pages formerly under /java/...

With this change, the redirects that you can see as context in the
patch below actually work again.

Applied.

Gerald

Index: .htaccess
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/.htaccess,v
retrieving revision 1.39
diff -u -r1.39 .htaccess
--- .htaccess	4 Dec 2016 23:33:28 -0000	1.39
+++ .htaccess	29 Dec 2016 21:51:18 -0000
@@ -48,12 +48,12 @@
 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/			https://gcc.gnu.org/
 Redirect permanent /java/gcj.html		https://gcc.gnu.org/
 Redirect permanent /java/libgcj.html		https://gcc.gnu.org/
 Redirect permanent /java/about.html		https://gcc.gnu.org/about.html
 Redirect permanent /java/FAQ.html		https://gcc.gnu.org/faq.html
 Redirect permanent /java/status.html		https://gcc.gnu.org/
+Redirect permanent /java/			https://gcc.gnu.org/
 
 Redirect permanent /bugs.html			https://gcc.gnu.org/bugs/
 Redirect permanent /c9xstatus.html		https://gcc.gnu.org/c99status.html

                 reply	other threads:[~2016-12-29 22:33 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.20.1612291802330.2994@anthias.pfeifer.com \
    --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).