public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Van Ly <van.ly@sdf.org>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs] Re: unreachable intro to gcc page linked to on readings page
Date: Thu, 1 Sep 2022 12:01:55 +0100	[thread overview]
Message-ID: <CAH6eHdR1HFj8_NtLbH8aRNygXGJxO4Z3Jh6-TN3fddU=bgCx_Q@mail.gmail.com> (raw)
In-Reply-To: <a9d5718e-329b-1a3d-de1e-09719a434403@pfeifer.com>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

On Mon, 29 Aug 2022 at 11:31, Gerald Pfeifer wrote:
>
> On Wed, 24 Aug 2022, Jonathan Wakely wrote:
> >> a broken link points to
> >>
> >>   An introduction to GCC by Brian J. Gough.
> >>   . http://www.network-theory.co.uk/gcc/intro/
> > There are much more recent archived copies like
> > https://web.archive.org/web/20181113021321/http://www.network-theory.co.uk/gcc/intro/
> > I'm not sure it's worth updating the link to an archived copy of that
> > page, because all the links for buying a PDF or printed copy are
> > probably dead now anyway.
> >
> > We could link to https://archive.org/details/B-001-002-835 instead, or
> > to the archived HTML version. The newest capture of the HTML version
> > seems to be this, although I didn't check that all pages are archived:
> > https://web.archive.org/web/20181206025406/http://www.network-theory.co.uk/docs/gccintro/
> > My preference would be to link to that latter. Although it's quite
> > dated, the sections on basic compilation and compiler flags are still
> > relevant for beginners.
> >
> > Gerald?
>
> I searched around a bit myself (since indeed the original and printed
> versions seem to be gone) and landed at
>
>    https://archive.org/details/B-001-002-835
>
> as well. I probably would have gone for that, though the
> web.archive.org/web link you found works equally if you want to point
> there instead.

Why not both?  I've pushed the attached patch to [wwwdocs].

[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 849 bytes --]

commit 0e4c9a39789b6dbcd44b2e0d4a42b5885d3bddb2
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Sep 1 10:57:46 2022 +0100

    Replace stale link to the "An Introduction to GCC" book

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 4269e9f0..5d1b78e8 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -22,8 +22,9 @@
 
 <ul>
 
-  <li><a href="http://www.network-theory.co.uk/gcc/intro/">An Introduction
-  to GCC</a> by Brian J. Gough.</li>
+  <li><a href="https://web.archive.org/web/20060106062936/http://www.network-theory.co.uk/gcc/intro/">An Introduction
+  to GCC</a> by Brian J. Gough
+  (<a href="https://archive.org/details/B-001-002-835/">e-book</a>).</li>
 
   <li><a href="https://en.wikibooks.org/wiki/GNU_C_Compiler_Internals">GNU C Compiler Internals (Wikibook)</a>, numerous contributors.</li>
 

  reply	other threads:[~2022-09-01 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07  8:33 Van Ly
2022-08-24 11:41 ` Jonathan Wakely
2022-08-29 10:31   ` Gerald Pfeifer
2022-09-01 11:01     ` Jonathan Wakely [this message]
2022-09-21  9:32       ` [wwwdocs] " Jonathan Wakely

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='CAH6eHdR1HFj8_NtLbH8aRNygXGJxO4Z3Jh6-TN3fddU=bgCx_Q@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=van.ly@sdf.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).