public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: [committed] doc: No longer generate old.html
Date: Sun, 24 Oct 2021 12:09:19 +0200 (CEST)	[thread overview]
Message-ID: <20211024100924.0B48133F04@hamza.pair.com> (raw)

Jonathan pointed this out to me while remove a link from the 
installation documentation to the no longer existing old.html 
page.

At first I was puzzled, but a bit of debugging made me realize
where the (now) empty old.html page still was coming from.

Fixed thusly, and I'll add some code to detect such situations
should they ever occur in the future.


Gerald


commit 4bd4138141330030b18960c204ebc1787cdaddf3
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun Oct 24 11:48:29 2021 +0200

    doc: No longer generate old.html
    
    Commit 431d26e1dd18c1146d3d4dcd3b45a3b04f7f7d59 removed
    doc/install-old.texi, alas we still tried to generate the
    associated web page old.html - which then turned out empty.
    
    Simplify remove this from the list of pages to be generated.
    
    gcc:
            * doc/install.texi2html: Do not generate old.html any longer.

diff --git a/gcc/doc/install.texi2html b/gcc/doc/install.texi2html
index 09bbbc425cd..001a869d0ea 100755
--- a/gcc/doc/install.texi2html
+++ b/gcc/doc/install.texi2html
@@ -46,9 +46,9 @@ fi
    echo "@set srcdir $SOURCEDIR/.."
 ) > $DESTDIR/gcc-vers.texi
 
-for x in index.html specific.html prerequisites.html download.html configure.html \
-         build.html test.html finalinstall.html binaries.html old.html \
-         gfdl.html
+for x in index.html specific.html prerequisites.html download.html \
+         configure.html build.html test.html finalinstall.html \
+         binaries.html gfdl.html
 do
     define=`echo $x | sed -e 's/\.//g'`
     echo "define = $define"

                 reply	other threads:[~2021-10-24 10:09 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=20211024100924.0B48133F04@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.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).