From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Janis Johnson <janis187@us.ibm.com>
Cc: Kelley Cook <KelleyCook@comcast.net>, <gcc-patches@gcc.gnu.org>,
<gcc@gcc.gnu.org>
Subject: Re: [wwwdocs] segfault.html (was Synthetic register related: Seg fault) - segfault.html [1/1]
Date: Thu, 16 Jan 2003 20:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0301161918260.27496-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20030116102124.A27760@us.ibm.com>
On Thu, 16 Jan 2003, Janis Johnson wrote:
> Gerald suggested that I create a new directory called bugs and move the
> current bugs.html to bugs/index.html, updating all of the places that
> reference the current file. Then reghunt-howto can be moved there, plus
Moving bugs.html is problematic - you can't just redirect with .htaccess
as is normal when moving files [1], because the URL given by installed
compilers is that on www.gnu.org and .htaccess doesn't get rewritten to
handle the different paths on www.gnu.org. Thus a bugs.html file needs to
stay around forever with a redirecting link (and maybe meta
http-equiv=refresh) for users accessing the www.gnu.org file.
[1] Apparently not documented in the GCC Coding Conventions, but we try to
avoid breaking people's links and bookmarks. For example, we use
.htaccess when renaming files (or merging one file into another), and all
the manuals for old releases in onlinedocs stay around forever even though
we only link to the manual for the most recent release in each release
series - someone might have the 2.95.2, 3.0.1, ... manual bookmarked or
linked to, and there are references to them in the list archives.
http://www.w3.org/Provider/Style/URI
http://www.useit.com/alertbox/981129.html
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2003-01-16 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 18:43 Synthetic register related: Seg fault Andy Walker
2003-01-15 19:46 ` Fergus Henderson
2003-01-15 20:01 ` Lars Segerlund
2003-01-16 18:03 ` [wwwdocs] segfault.html (was Synthetic register related: Seg fault) - segfault.html [1/1] Kelley Cook
2003-01-16 19:33 ` Janis Johnson
2003-01-16 20:06 ` Joseph S. Myers [this message]
2003-01-16 21:03 ` Janis Johnson
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=Pine.LNX.4.33.0301161918260.27496-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=KelleyCook@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.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).