From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: drkm <darkman_spam@yahoo.fr>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: PATCH for Re: Broken link on <URL:http://gcc.gnu.org/projects/beginner.html>
Date: Wed, 02 Apr 2003 10:54:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.53.0304021035520.14072@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20030402001352.72175.qmail@web40908.mail.yahoo.com>
On Wed, 2 Apr 2003, drkm wrote:
> As written on footer of
> <URL:http://gcc.gnu.org/projects/beginner.html>, I address you this
> mail, I hope I don't make a mistake.
Now, it's perfectly fine.
> On the above page, there is a broken link, in section
> "Documentation". The link is named "The GNU Compiler Writer's Jump
> Point" and point to <URL:http://members.wri.com/johnnyb/compilers/>,
> which results on a 404 HTTP error. I found
> <URL:http://www.eskimo.com/~johnnyb/computers/toy/>, which I think is
> the same (same title and same site owner username in the URL).
We already have the (correct) link on our readings.html page, so I think
it's best to remove the redundancy.
Thanks for letting us know!
Gerald
Remove broken link to johnnyb's page, which is already linked from
readings.html.
Index: projects/beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.33
diff -u -3 -p -r1.33 beginner.html
--- projects/beginner.html 27 Jan 2003 11:20:30 -0000 1.33
+++ projects/beginner.html 2 Apr 2003 08:35:42 -0000
@@ -909,10 +909,8 @@ place. It belongs in the official manua
href="http://gcc.gnu.org/onlinedocs/gccint/Trees.html">C/C++ specific manual</a>, and a
<a href="http://www.ncsa.uiuc.edu/~wendling/tree.html">third party,
general manual</a>. Both of them are incomplete. Several people have
-written partial manuals on implementing new front ends: look at <a
-href="http://members.wri.com/johnnyb/compilers/">The GNU Compiler
-Writer's Jump Point</a> and our <a
-href="../readings.html">readings list</a>.</p>
+written partial manuals on implementing new front ends: look at our
+<a href="../readings.html">readings list</a>.</p>
<p>Michael Dupont <<a
href="mailto:mdupont777@yahoo.com">mdupont777@yahoo.com</a>>
prev parent reply other threads:[~2003-04-02 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 2:50 drkm
2003-04-02 10:54 ` Gerald Pfeifer [this message]
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.BSF.4.53.0304021035520.14072@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=darkman_spam@yahoo.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).