fix many internal links

Fixed a number of internal links that need to
go to the GitHub site.

Ran `make www` to perform the above.

1984/decot/README.md

@@ -71,8 +71,8 @@ to:
     for(signal=0;*k *x * __FILE__ *i;) do {
 ```
 
-To see what we mean look at the [original source file](decot.orig.c). The
-[alternate code](decot.alt.c) is the version that has this modification. The
+To see what we mean look at the [original source file](%%REPO_URL%%/1984/decot/decot.orig.c). The
+[alternate code](%%REPO_URL%%/1984/decot/decot.alt.c) is the version that has this modification. The
 fixed version has instead:
 
 ``` <!---c-->

1984/decot/index.html

@@ -406,8 +406,8 @@ changed it from:</p>
 <pre><code>    for(signal=0;*k * x * __FILE__ *i;) do {</code></pre>
 <p>to:</p>
 <pre><code>    for(signal=0;*k *x * __FILE__ *i;) do {</code></pre>
-<p>To see what we mean look at the <a href="decot.orig.c">original source file</a>. The
-<a href="decot.alt.c">alternate code</a> is the version that has this modification. The
+<p>To see what we mean look at the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/decot/decot.orig.c">original source file</a>. The
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/decot/decot.alt.c">alternate code</a> is the version that has this modification. The
 fixed version has instead:</p>
 <pre><code>    for(signal=0;*k *= * __FILE__ *i;) do {</code></pre>
 <h2 id="authors-remarks">Author’s remarks:</h2>

1984/mullender/README.md

@@ -125,8 +125,8 @@ favorite entries!
 In 2023 remarks were discovered from [Sjoerd
 Mullender](../../authors.html#Sjoerd_Mullender), one of the authors, and so was the
 program that was used by the authors to generate the array that he referred to.
-Because [a.out.h](a.out.h), which [gentab.c](gentab.c) uses, is not available in
-all systems (like macOS) and more importantly because we wanted it to be as
+Because [a.out.h](%%REPO_URL%%/1984/mullender/a.out.h), which [gentab.c](%%REPO_URL%%/1984/mullender/gentab.c) uses,
+is not available in all systems (like macOS) and more importantly because we wanted it to be as
 close to as the original as possible we used a copy of
 <https://raw.githubusercontent.com/dspinellis/unix-history-repo/Research-Release/usr/include/a.out.h>
 in the *fabulous* [Unix History
@@ -386,7 +386,7 @@ format randomly. So we wrote a program to choose an appropriate format at
 random. The program we wrote for that follows.  This program actually also
 extracted the machine code from the object file.
 
-NOTE from judges: see [gentab.c](gentab.c) for a copy of this file that can be
+NOTE from judges: see [gentab.c](%%REPO_URL%%/1984/mullender/gentab.c) for a copy of this file that can be
 compiled in modern systems.
 
 ``` <!---c-->

1984/mullender/index.html

@@ -456,8 +456,8 @@ favorite entries!</p>
 <p>In 2023 remarks were discovered from <a href="../../authors.html#Sjoerd_Mullender">Sjoerd
 Mullender</a>, one of the authors, and so was the
 program that was used by the authors to generate the array that he referred to.
-Because <a href="a.out.h">a.out.h</a>, which <a href="gentab.c">gentab.c</a> uses, is not available in
-all systems (like macOS) and more importantly because we wanted it to be as
+Because <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/mullender/a.out.h">a.out.h</a>, which <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/mullender/gentab.c">gentab.c</a> uses,
+is not available in all systems (like macOS) and more importantly because we wanted it to be as
 close to as the original as possible we used a copy of
 <a href="https://raw.githubusercontent.com/dspinellis/unix-history-repo/Research-Release/usr/include/a.out.h" class="uri">https://raw.githubusercontent.com/dspinellis/unix-history-repo/Research-Release/usr/include/a.out.h</a>
 in the <em>fabulous</em> <a href="https://github.com/dspinellis/unix-history-repo/tree/Research-Release">Unix History
@@ -661,7 +661,7 @@ formats for each constant in the resulting array, and we wanted to choose the
 format randomly. So we wrote a program to choose an appropriate format at
 random. The program we wrote for that follows. This program actually also
 extracted the machine code from the object file.</p>
-<p>NOTE from judges: see <a href="gentab.c">gentab.c</a> for a copy of this file that can be
+<p>NOTE from judges: see <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/mullender/gentab.c">gentab.c</a> for a copy of this file that can be
 compiled in modern systems.</p>
 <pre><code>    #include &lt;stdio.h&gt;
     #include &lt;a.out.h&gt;