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.

1994/dodsond2/README.md

@@ -84,8 +84,8 @@ in an effort to get around the 1994 version of Rule 2:
        followed by either whitespace or end of file, must be <= 1536.
 ```
 
-Indeed, when [dodsond2.gz](dodsond2.gz) is uncompressed, it is identical
-to the [dodsond2.c](%%REPO_URL%%/1994/dodsond2/dodsond2.c) file you find today.
+Indeed the [dodsond2.c](%%REPO_URL%%/1994/dodsond2/dodsond2.c) file is
+what you find today.
 
 The IOCCC rules and guidelines were modified in an effort to address
 this fun "_abuse of the rules_" style hack.

1994/dodsond2/index.html

@@ -414,8 +414,8 @@ in an effort to get around the 1994 version of Rule 2:</p>
 <pre><code>    2) Your entry must be &lt;= 3217 bytes in length.  The number of characters
        excluding whitespace (tab, space, newline), and excluding any ; { or }
        followed by either whitespace or end of file, must be &lt;= 1536.</code></pre>
-<p>Indeed, when <a href="dodsond2.gz">dodsond2.gz</a> is uncompressed, it is identical
-to the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/dodsond2/dodsond2.c">dodsond2.c</a> file you find today.</p>
+<p>Indeed the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/dodsond2/dodsond2.c">dodsond2.c</a> file is
+what you find today.</p>
 <p>The IOCCC rules and guidelines were modified in an effort to address
 this fun “<em>abuse of the rules</em>” style hack.</p>
 <p>It is worth noting that without this compression “<em>abuse of the rules</em>”

1994/shapiro/README.md

@@ -51,7 +51,7 @@ source file is self documenting.  :-)
 From time to time, run `ps(1)` and look at the new processes.
 
 See [shapiro.html](shapiro.html) for more information in the internals of this program.
-The file [shapiro.alt.c](shapiro.alt.c) contains a non-obfuscated version of
+The file [shapiro.alt.c](%%REPO_URL%%/1994/shapiro/shapiro.alt.c) contains a non-obfuscated version of
 this program. Note that this alt file is currently missing. See
 [1994 shapiro bugs](../../bugs.html#1994_shapiro) for details.
 
@@ -67,18 +67,18 @@ The basic theme (pun) of this program is:
 ```
 
 
-My entry ([shapiro.c](shapiro.c)) is mostly comments, formatted in the shape of a
+My entry ([shapiro.c](%%REPO_URL%%/1994/shapiro/shapiro.c)) is mostly comments, formatted in the shape of a
 clock. If you strip out the comments and look at the code you will
 quickly realize that the comments were the important part and that
 the code does very little (see pun above). It writes (to `stdout`)
-another C program ([shapiro_t2.c](shapiro_t2.c)). This is the first level of
+another C program ([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c)). This is the first level of
 obfuscation.
 
-The second program ([shapiro_t2.c](shapiro_t2.c) (use `make everything` first)
+The second program ([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c) (use `make everything` first)
 prints a clock in the upper right hand corner of your VTxxx/ANSI display.
 
 Most of the surface obfuscation in the second program
-([shapiro_t2.c](shapiro_t2.c)) was an attempt to make it as small as possible.
+([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c)) was an attempt to make it as small as possible.
 You should be able to see around this with `cb(1)` and some more intelligent
 variable names.  Once you get past this you will realize that the third level of
 obfuscation is a six member client/server hierarchy.  (See the

1994/shapiro/index.html

@@ -403,23 +403,23 @@ bring it back to the foreground.</p>
 source file is self documenting. :-)</p>
 <p>From time to time, run <code>ps(1)</code> and look at the new processes.</p>
 <p>See <a href="shapiro.html">shapiro.html</a> for more information in the internals of this program.
-The file <a href="shapiro.alt.c">shapiro.alt.c</a> contains a non-obfuscated version of
+The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/shapiro/shapiro.alt.c">shapiro.alt.c</a> contains a non-obfuscated version of
 this program. Note that this alt file is currently missing. See
 <a href="../../bugs.html#1994_shapiro">1994 shapiro bugs</a> for details.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>The basic theme (pun) of this program is:</p>
 <pre><code>    &quot;This time (everything) is not where it should be.&quot;
           ~~~~</code></pre>
-<p>My entry (<a href="shapiro.c">shapiro.c</a>) is mostly comments, formatted in the shape of a
+<p>My entry (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/shapiro/shapiro.c">shapiro.c</a>) is mostly comments, formatted in the shape of a
 clock. If you strip out the comments and look at the code you will
 quickly realize that the comments were the important part and that
 the code does very little (see pun above). It writes (to <code>stdout</code>)
-another C program (<a href="shapiro_t2.c">shapiro_t2.c</a>). This is the first level of
+another C program (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/shapiro/shapiro_t2.c">shapiro_t2.c</a>). This is the first level of
 obfuscation.</p>
-<p>The second program (<a href="shapiro_t2.c">shapiro_t2.c</a> (use <code>make everything</code> first)
+<p>The second program (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/shapiro/shapiro_t2.c">shapiro_t2.c</a> (use <code>make everything</code> first)
 prints a clock in the upper right hand corner of your VTxxx/ANSI display.</p>
 <p>Most of the surface obfuscation in the second program
-(<a href="shapiro_t2.c">shapiro_t2.c</a>) was an attempt to make it as small as possible.
+(<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/shapiro/shapiro_t2.c">shapiro_t2.c</a>) was an attempt to make it as small as possible.
 You should be able to see around this with <code>cb(1)</code> and some more intelligent
 variable names. Once you get past this you will realize that the third level of
 obfuscation is a six member client/server hierarchy. (See the

1994/weisberg/README.md

@@ -77,7 +77,7 @@ event of a system shutdown or reboot.
 
 ### Bugs
 
-The alternative version ([weisberg.alt.c](weisberg.alt.c)) has never actually run
+The alternative version ([weisberg.alt.c](%%REPO_URL%%/1994/weisberg/weisberg.alt.c)) has never actually run
 to completion. After running for close to a week it had reached somewhere around
 250e6, when it became necessary to test the reboot feature (which worked
 remarkably well). As there are quite a lot of primes to be found before reaching

1994/weisberg/index.html

@@ -413,7 +413,7 @@ run to completion, so as an added feature, it will cease execution upon
 reception of a signal (any will do equally well), as well as in the
 event of a system shutdown or reboot.</p>
 <h3 id="bugs">Bugs</h3>
-<p>The alternative version (<a href="weisberg.alt.c">weisberg.alt.c</a>) has never actually run
+<p>The alternative version (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/weisberg.alt.c">weisberg.alt.c</a>) has never actually run
 to completion. After running for close to a week it had reached somewhere around
 250e6, when it became necessary to test the reboot feature (which worked
 remarkably well). As there are quite a lot of primes to be found before reaching

1994/westley/README.md

@@ -85,7 +85,7 @@ compiler line you will get a different message (**as compiler errors** due to
 
 _This is independent of the previous (if there are any previous) compiler
 invocations_ specified. That means with the right compiler invocation you can
-'win' the game on the first go. But unlike the [alternate code](westley.alt.c),
+'win' the game on the first go. But unlike the [alternate code](%%REPO_URL%%/1994/westley/westley.alt.c),
 you do not run this program as it will not compile: instead it will be compiler
 error messages; there is no running the program.
 

1994/westley/index.html

@@ -427,7 +427,7 @@ compiler line you will get a different message (<strong>as compiler errors</stro
 (escape the dungeon) and others will show something else.</p>
 <p><em>This is independent of the previous (if there are any previous) compiler
 invocations</em> specified. That means with the right compiler invocation you can
-‘win’ the game on the first go. But unlike the <a href="westley.alt.c">alternate code</a>,
+‘win’ the game on the first go. But unlike the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.alt.c">alternate code</a>,
 you do not run this program as it will not compile: instead it will be compiler
 error messages; there is no running the program.</p>
 <h3 id="original-try">Original try:</h3>