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.

2004/README.md

@@ -26,11 +26,11 @@ local compiler.
 ## Remarks on some of the entries
 
 We believe you will be impressed with this year's winning entries.  The [Best of
-Show](gavin/gavin.c) is a fine example of obfuscation.  But don't ignore the
+Show](%%REPO_URL%%/2004/gavin/gavin.c) is a fine example of obfuscation.  But don't ignore the
 other entries!  There are games, utilities, programs that output images and a
 one-liner that is incredibly compact for what it can do.
 
-The [Best Abuse of the Guidelines](hibachi/hibachi.c) is technically allowed by
+The [Best Abuse of the Guidelines](%%REPO_URL%%/2004/hibachi/hibachi.c) is technically allowed by
 the rules.  This year we allowed it due to the functionality of the program.
 This entry is one of the easiest to read!  Don't assume you can win using
 similar techniques next time ... :-)

2004/index.html

@@ -379,11 +379,11 @@ require certain changes (add or remove a library, add or remove a
 yours is lacking, you may need to compile using <code>gcc</code> instead of your
 local compiler.</p>
 <h2 id="remarks-on-some-of-the-entries">Remarks on some of the entries</h2>
-<p>We believe you will be impressed with this year’s winning entries. The <a href="gavin/gavin.c">Best of
+<p>We believe you will be impressed with this year’s winning entries. The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavin/gavin.c">Best of
 Show</a> is a fine example of obfuscation. But don’t ignore the
 other entries! There are games, utilities, programs that output images and a
 one-liner that is incredibly compact for what it can do.</p>
-<p>The <a href="hibachi/hibachi.c">Best Abuse of the Guidelines</a> is technically allowed by
+<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/hibachi/hibachi.c">Best Abuse of the Guidelines</a> is technically allowed by
 the rules. This year we allowed it due to the functionality of the program.
 This entry is one of the easiest to read! Don’t assume you can win using
 similar techniques next time … :-)</p>

2004/jdalbec/README.md

@@ -114,7 +114,7 @@ last digit.  Four common elements could also be written as isotopes of these two
 elements: `He=Np(2)`, `Li=Pu(2)`, `Ta=Np(3)`, `W=Pu(3)`.  To get other isotopes,
 just change the last digit to a number greater than 3.
 
-The build file runs [jdalbec.c](jdalbec.c) through the C preprocessor to
+The build file runs [jdalbec.c](%%REPO_URL%%/2004/jdalbec/jdalbec.c) through the C preprocessor to
 generate `jdalbec2.c` which is edited with `ed(1)` (NOTE: this was
 changed to `sed(1)` by the judges) to correct spacing
 problems caused by some preprocessors.  (I know you dislike
@@ -122,10 +122,10 @@ Perl, but hopefully `ed(1)` is more common on POSIX systems than
 Perl.)  The build file then compiles `jdalbec2.c]` and removes the
 `jdalbec2.c` file.
 
-I don't think I'm abusing the [Makefile](Makefile) since I'm only using
+I don't think I'm abusing the [Makefile](%%REPO_URL%%/2004/jdalbec/Makefile) since I'm only using
 147 characters including white space and the `#!` line and the
 commented-out `-Wall -pedantic` options.  The [rules for the
-16th IOCCC](../../2004/rules.txt) specifically allowed build files up to 521
+16th IOCCC](../rules.txt) specifically allowed build files up to 521
 characters long so my build file would have been well within
 those limits.  (What typo?)
 
@@ -168,7 +168,7 @@ line 3 because the compiler doesn't recognize `??=` as a trigraph
 step on Mac OS X 10.1.5 generates lots of errors in "smart
 mode" because the "smart" preprocessor expects a valid C
 program as input.  The preprocessor then falls back to "basic
-mode" and preprocesses [jdalbec.c](jdalbec.c) successfully without warnings,
+mode" and preprocesses [jdalbec.c](%%REPO_URL%%/2004/jdalbec/jdalbec.c) successfully without warnings,
 even when I give it the `-Wall -pedantic` options.  It inserts
 a lot of extra spaces into the preprocessed output which is
 why I had to add the `ed(1)` step to the build file so that my
@@ -191,7 +191,7 @@ it if you run into this feature (e.g. `1 22` instead of `122`).
 Note: you may want to be sure you have a limit on stack size before trying this.
 I ran it on Debian GNU/Linux and discovered that I did not have a limit on stack
 size.  Fortunately the OS killed the process after a while.  This is consistent
-with the output of [1996/schweikh3](../../1996/schweikh3/schweikh3.c) which reports
+with the output of [1996/schweikh3](%%REPO_URL%%/1996/schweikh3/schweikh3.c) which reports
 `malloc lied!  Killed by SIGKILL`.
 
 Arguments matching `/(?:.){10,}/` will produce visually incorrect

2004/jdalbec/index.html

@@ -434,16 +434,16 @@ the <a href="https://en.wikipedia.org/wiki/Isotope">isotopes</a> of
 last digit. Four common elements could also be written as isotopes of these two
 elements: <code>He=Np(2)</code>, <code>Li=Pu(2)</code>, <code>Ta=Np(3)</code>, <code>W=Pu(3)</code>. To get other isotopes,
 just change the last digit to a number greater than 3.</p>
-<p>The build file runs <a href="jdalbec.c">jdalbec.c</a> through the C preprocessor to
+<p>The build file runs <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/jdalbec.c">jdalbec.c</a> through the C preprocessor to
 generate <code>jdalbec2.c</code> which is edited with <code>ed(1)</code> (NOTE: this was
 changed to <code>sed(1)</code> by the judges) to correct spacing
 problems caused by some preprocessors. (I know you dislike
 Perl, but hopefully <code>ed(1)</code> is more common on POSIX systems than
 Perl.) The build file then compiles <code>jdalbec2.c]</code> and removes the
 <code>jdalbec2.c</code> file.</p>
-<p>I don’t think I’m abusing the <a href="Makefile">Makefile</a> since I’m only using
+<p>I don’t think I’m abusing the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/Makefile">Makefile</a> since I’m only using
 147 characters including white space and the <code>#!</code> line and the
-commented-out <code>-Wall -pedantic</code> options. The <a href="../../2004/rules.txt">rules for the
+commented-out <code>-Wall -pedantic</code> options. The <a href="../rules.txt">rules for the
 16th IOCCC</a> specifically allowed build files up to 521
 characters long so my build file would have been well within
 those limits. (What typo?)</p>
@@ -481,7 +481,7 @@ line 3 because the compiler doesn’t recognize <code>??=</code> as a trigraph
 step on Mac OS X 10.1.5 generates lots of errors in “smart
 mode” because the “smart” preprocessor expects a valid C
 program as input. The preprocessor then falls back to “basic
-mode” and preprocesses <a href="jdalbec.c">jdalbec.c</a> successfully without warnings,
+mode” and preprocesses <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/jdalbec.c">jdalbec.c</a> successfully without warnings,
 even when I give it the <code>-Wall -pedantic</code> options. It inserts
 a lot of extra spaces into the preprocessed output which is
 why I had to add the <code>ed(1)</code> step to the build file so that my
@@ -500,7 +500,7 @@ it if you run into this feature (e.g. <code>1 22</code> instead of <code>122</c
 <p>Note: you may want to be sure you have a limit on stack size before trying this.
 I ran it on Debian GNU/Linux and discovered that I did not have a limit on stack
 size. Fortunately the OS killed the process after a while. This is consistent
-with the output of <a href="../../1996/schweikh3/schweikh3.c">1996/schweikh3</a> which reports
+with the output of <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh3/schweikh3.c">1996/schweikh3</a> which reports
 <code>malloc lied!  Killed by SIGKILL</code>.</p>
 <p>Arguments matching <code>/(?:.){10,}/</code> will produce visually incorrect
 results (e.g., generation 1 starting from 1111111111 will

2004/kopczynski/README.md

@@ -101,7 +101,7 @@ the number from 8 to 11 that it thinks it is.
   (`$?` is shorter)
 
 * I achieved some additional tightness by `-Dif=while` which saved 9 chars of
-source for the cost of 11 chars of the [Makefile](Makefile). If I used
+source for the cost of 11 chars of the [Makefile](%%REPO_URL%%/2004/kopczynski/Makefile). If I used
 `-DB=while`, I would save 12 for 10, but I think the current version is slightly
 more obfuscated.
 

2004/kopczynski/index.html

@@ -436,7 +436,7 @@ number, not to print it, but if you think otherwise, the change would
 cost 6 chars (plus a warning). Change <code>return *</code> to <code>printf("%d",*)</code>.
 (<code>$?</code> is shorter)</p></li>
 <li><p>I achieved some additional tightness by <code>-Dif=while</code> which saved 9 chars of
-source for the cost of 11 chars of the <a href="Makefile">Makefile</a>. If I used
+source for the cost of 11 chars of the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/kopczynski/Makefile">Makefile</a>. If I used
 <code>-DB=while</code>, I would save 12 for 10, but I think the current version is slightly
 more obfuscated.</p></li>
 </ul>