mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

change references to post Great Fork Merge URLs

Browse Source 
In preparation for the **Great Fork Merge**:

We change references for the repo from
`https://github.com/ioccc-src/temp-test-ioccc`
to `https://github.com/ioccc-src/winner`.

We change references for the web site from
`https://ioccc-src.github.io/temp-test-ioccc`
to `https://github.com/ioccc-src/winner`.

NOTE: There will be a **LOT OF LINKS BROKEN**, because of the changes
to the REPO URL and the WEBSITE URL, until the **Great Fork Merge**
updates the+[official IOCCC website](https://www.ioccc.org).
This commit is contained in:
Landon Curt Noll committed 2024-12-28 21:56:40 -08:00
1 parent 1d264105d2
commit 6b950a2e3c
452 files changed
+17037 -16746
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

faq.html
+28 -28
View File
@@ -412,7 +412,7 @@
<!-- START: this line starts content from: inc/navbar.empty.html -->
<div class="navbar">
<a class="Right" href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Ffaq.html">&#x2713;</a>
<a class="Right" href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.ioccc.org%2Ffaq.html">&#x2713;</a>
</div>
<!-- END: this line ends content from: inc/navbar.empty.html -->
@@ -850,7 +850,7 @@ or <a href="https://unix.org/online.html">later SUS</a>.</p>
(renamed as <code>Makefile</code> of course) as a starting point for your
entry’s <code>Makefile</code>:</p>
<ul>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">view example Makefile</a></li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/next/Makefile.example">view example Makefile</a></li>
<li><a href="next/Makefile.example">Makefile.example</a></li>
</ul>
<p>The <code>Makefile</code> is a file used by the <code>make(1)</code> command that contains
@@ -957,9 +957,9 @@ rounds; we look at the author name only if an entry wins. See the
invoke your program, perhaps using other commonly installed tools (or tools
included in your submission), it can be helpful to include a <code>try.sh</code> script:</p>
<ul>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/try.sh">view example try.sh</a></li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/next/try.sh">view example try.sh</a></li>
<li><a href="next/try.sh">download example try.sh</a></li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/try.alt.sh">view example try.alt.sh</a></li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/next/try.alt.sh">view example try.alt.sh</a></li>
<li><a href="next/try.alt.sh">download example try.alt.sh</a></li>
</ul>
<p>The template <code>try.sh</code> script can be used as a starting point, or you can look at
@@ -2325,7 +2325,7 @@ or <code>Anonymous_year.digits</code>.</p>
<p>The latter form is in case there are more than one anonymous author in a given
year.</p>
<p><strong>NOTE</strong>: even if the directory name is not <code>anonymous</code> the above rules apply as in
in the case of <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/anon/anon.c">2005/anon</a>.</p>
in the case of <a href="https://github.com/ioccc-src/winner/blob/master/2005/anon/anon.c">2005/anon</a>.</p>
<p>Anonymous <code>author_handle</code>’s match this regexp:</p>
<pre><code> Anonymous_[0-9][0-9][0-9][0-9][.0-9]*$</code></pre>
<p>Jump to: <a href="#">top</a></p>
@@ -2362,7 +2362,7 @@ See <a href="https://www.json.org/json-en.html" class="uri">https://www.json.org
spec</em>.</p>
<p>A good way to understand the JSON file contents of a <code>author_handle.json</code> file
is to look at an example, for instance the <code>author_handle.json</code> file for Yusuke
Endoh, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/author/Yusuke_Endoh.json">author/Yusuke_Endoh.json</a>.</p>
Endoh, <a href="https://github.com/ioccc-src/winner/blob/master/author/Yusuke_Endoh.json">author/Yusuke_Endoh.json</a>.</p>
<p>As of <em>Thu Nov 30 23:51:12 UTC 2023</em>, it was:</p>
<pre><code> {
&quot;no_comment&quot; : &quot;mandatory comment: because comments were removed from the original JSON spec&quot;,
@@ -2695,7 +2695,7 @@ line link, you will be taken to that author’s <code>author_handle.json</code>
<p>For example, <a href="authors.html#Brian_Westley">Brian Westley</a> can view his
author entry and see that his <em>author_handle</em> is <strong>Brian_Westley</strong>.
Clicking on the <em>author_handle</em> shows the contents of
the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/author/Brian_Westley.json">Brian_Westley.json</a> file.</p>
the <a href="https://github.com/ioccc-src/winner/blob/master/author/Brian_Westley.json">Brian_Westley.json</a> file.</p>
<p><strong>IMPORTANT NOTE</strong>: An <code>author</code> who has won a previous IOCCC is encouraged to reuse their
<code>author_handle</code> so that new winning entries can be associated with the same author.</p>
<p>See
@@ -2745,7 +2745,7 @@ See <a href="https://www.json.org/json-en.html" class="uri">https://www.json.org
spec</em>.</p>
<p>A good way to understand the JSON file contents of a <code>.entry.json</code> file
is to look at an example, for instance the
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/.entry.json">1984/laman/.entry.json</a> file, as
<a href="https://github.com/ioccc-src/winner/blob/master/1984/laman/.entry.json">1984/laman/.entry.json</a> file, as
it is shorter than some of the others.</p>
<p>As of <em>Fri 26 Jul 2024 17:29:15 UTC</em>, it contains:</p>
<pre><code> {
@@ -4184,10 +4184,10 @@ where it’s quite easy to see the differences).</p>
very easily. To do that <code>cd 1991/dds</code> and then do:</p>
<pre><code> make diff_alt_prog</code></pre>
<p>and you’ll see a single line changed and very simply.</p>
<p><strong>NOTE</strong>: The above mentioned <code>make</code> rules are located in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1337.mk">1337.mk</a>
<p><strong>NOTE</strong>: The above mentioned <code>make</code> rules are located in the <a href="https://github.com/ioccc-src/winner/blob/master/1337.mk">1337.mk</a>
include Makefile via the optional include directive line:</p>
<pre><code> -include 1337.mk ../1337.mk ../../1337.mk</code></pre>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1337.mk">1337.mk</a> file must exist in the current
<p>The <a href="https://github.com/ioccc-src/winner/blob/master/1337.mk">1337.mk</a> file must exist in the current
directory, or under the directory above, or under the directory 2 levels
above in order for these rules to work.</p>
<p>If you’re an IOCCC masochist :-), or you really want even more details, very often the
@@ -4253,7 +4253,7 @@ remarks and always the author’s or authors’ remarks, you look at the origina
code. When the entry source code is called <code>prog.c</code> the original code is in
<code>prog.orig.c</code>; otherwise it is <code>dirname.orig.c</code>. For instance one of Landon’s all
time favourite entries is <a href="1984/mullender/index.html">1984/mullender</a> and the
original code is in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/mullender/mullender.orig.c">mullender.orig.c</a>. In
original code is in <a href="https://github.com/ioccc-src/winner/blob/master/1984/mullender/mullender.orig.c">mullender.orig.c</a>. In
some cases, such as <code>1984/mullender</code>, the original code is the same as the code
as no changes were made (there is an alt version for systems that are not
VAX-11/PDP-11, however).</p>
@@ -4551,7 +4551,7 @@ it will be that. For instance using the above example you might do:</p>
<h4 id="making-changes-fixes-etc.">Making changes, fixes etc.</h4>
<p>Here you must use your wits, knowledge, creativity and whatever else you have.
Let’s say that Cody wants to update his file
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson1/play.sh">2020/ferguson1/play.sh</a> script. He would open it in
<a href="https://github.com/ioccc-src/winner/blob/master/2020/ferguson1/play.sh">2020/ferguson1/play.sh</a> script. He would open it in
his editor of choice (in his case vim) and make the changes. He would then make
sure (as there is a last updated date) to update the last updated date. For
instance he might add the following:</p>
@@ -4583,7 +4583,7 @@ with your ssh key. To do this you need to do:</p>
<p>Now you’d be ready to make your commits.</p>
<p>Before doing anything else, however, a new branch needs to be created.
Continuing the example above for
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson1/play.sh">2020/ferguson1/play.sh</a>, it might be that:</p>
<a href="https://github.com/ioccc-src/winner/blob/master/2020/ferguson1/play.sh">2020/ferguson1/play.sh</a>, it might be that:</p>
<pre><code> git checkout -B human-snakes</code></pre>
<p>This would change the branch to the newly created branch <code>human-snakes</code> branch.
Now Cody could commit the changes:</p>
@@ -4676,7 +4676,7 @@ website problem, we ask that you first look at the <a href="https://github.com/i
issues</a> to see if the problem has
already been reported. If it has been reported, feel free to add a comment to
the issue. Otherwise, if you do not see the same issue reported, then feel free
to <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/new?assignees=&amp;labels=website&amp;projects=&amp;template=website_issue.yml&amp;title=%5BWebsite%5D+%3Ctitle%3E">open a new IOCCC website issue</a>.</p>
to <a href="https://github.com/ioccc-src/winner/issues/new?assignees=&amp;labels=website&amp;projects=&amp;template=website_issue.yml&amp;title=%5BWebsite%5D+%3Ctitle%3E">open a new IOCCC website issue</a>.</p>
<p>Jump to: <a href="#">top</a></p>
<div id="fix_website">
<h3 id="q-9.5-how-can-i-submit-a-fix-to-the-ioccc-website">Q 9.5: How can I submit a fix to the IOCCC website?</h3>
@@ -4779,7 +4779,7 @@ quicker <code>make quick_www</code> as this can speed up your testing.</p>
<code>location.html</code> pages and it will also check the timestamps of the <code>index.html</code>
files versus the <code>README.md</code> files. Since they were touched and thus the
timestamp was updated, the
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/bin/quick-readme2index.sh">bin/quick-readme2index.sh</a> tool would
<a href="https://github.com/ioccc-src/winner/blob/master/bin/quick-readme2index.sh">bin/quick-readme2index.sh</a> tool would
only worry about those two files. This greatly speeds things along while testing.
Nevertheless, doing a final <code>make www</code> is still recommended best practice
before you form your pull request.</p>
@@ -4920,7 +4920,7 @@ possible it would be good to include them in the discussion as well (see below)
as it is <strong>very likely</strong> there are things that will be missed when trying to
deobfuscate the code, some of which might be important to the author.</p>
<p>To contribute your <strong>deobfuscated</strong> code, please open up a
<a href="https://github.com/ioccc-src/temp-test-ioccc/discussions/new?category=show-and-tell">Show and tell new discussion</a>
<a href="https://github.com/ioccc-src/winner/discussions/new?category=show-and-tell">Show and tell new discussion</a>
with a title of the form:</p>
<blockquote>
<p>Enhancement: deobfuscated code for YYYY/dirname</p>
@@ -5081,14 +5081,14 @@ exaggeration</a>.</p>
</div>
</div>
</div>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/.top">.top</a> file resides at the top directory. This file contains the complete list
<p>The <a href="https://github.com/ioccc-src/winner/blob/master/.top">.top</a> file resides at the top directory. This file contains the complete list
of IOCCC years.</p>
<p>Under each IOCCC year, one will find a <code>.year</code> file. These files contain directory paths from the top directory,
of the IOCCC entry directories for a given year. For example, see the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/.year">1984/.year</a> file.</p>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/.allyear">.allyear</a> file contains the contents of all <code>.year</code> files for all IOCCC years.</p>
of the IOCCC entry directories for a given year. For example, see the <a href="https://github.com/ioccc-src/winner/blob/master/1984/.year">1984/.year</a> file.</p>
<p>The <a href="https://github.com/ioccc-src/winner/blob/master/.allyear">.allyear</a> file contains the contents of all <code>.year</code> files for all IOCCC years.</p>
<p>Under each IOCCC entry directory, you will find a <code>.path</code> file.
These files contain the directory path from the top directory.
For example see <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/anonymous/.path">1984/anonymous/.path</a>.</p>
For example see <a href="https://github.com/ioccc-src/winner/blob/master/1984/anonymous/.path">1984/anonymous/.path</a>.</p>
<p>The .top, .allyear, .year and .path files are generated from the top level Makefile, by:</p>
<pre><code> make genpath</code></pre>
<p>Jump to: <a href="#">top</a></p>
@@ -5254,7 +5254,7 @@ the words:</p>
<p>at the top right corner; clicking on this will take you to the <a href="nojs-menu.html">no JavaScript
menu</a> which is a plaintext menu. You of course can use this if
you like, even if you do not have JavaScript enabled, by pointing your browser
to <a href="https://ioccc-src.github.io/temp-test-ioccc/nojs-menu.html" class="uri">https://ioccc-src.github.io/temp-test-ioccc/nojs-menu.html</a>.</p>
to <a href="https://www.ioccc.org/nojs-menu.html" class="uri">https://www.ioccc.org/nojs-menu.html</a>.</p>
<div id="tablet_menu">
<h5 id="menus-on-tablet-devices-e.g.-ipads">Menus on tablet devices (e.g. iPads)</h5>
</div>
@@ -5288,7 +5288,7 @@ and landscape mode.</p>
menu</a>. If you have a fix for this that <strong>does NOT
affect the usability of desktops, laptops or other mobile devices</strong>, please
consider fixing it and <a href="#pull_request">opening a pull request</a> or at
least <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/new/choose">report it as an
least <a href="https://github.com/ioccc-src/winner/issues/new/choose">report it as an
issue</a> (choose
the category <em>Website issue</em>).</p>
<p>Jump to: <a href="#">top</a></p>
@@ -5464,7 +5464,7 @@ as shown in the <a href="https://web.archive.org">Internet Wayback Machine</a>
<a href="https://web.archive.org/web/20210102042216/www.ioccc.org/years.html">snapshot of 2021 Jan 02</a>
were the first IOCCC entries to have been released via
<a href="https://git-scm.com">git</a> and <a href="https://github.com">GitHub</a>.</p>
<h4 id="dec-30-thru-202y-mmm-dd---work-on-the-temp-test-ioccc-github-repo">2020 Dec 30 thru 202y MMM DD - Work on the temp-test-ioccc GitHub repo</h4>
<h4 id="dec-30-thru-2024-dec-28---work-on-the-temp-test-ioccc-github-repo">2020 Dec 30 thru 2024 Dec 28 - Work on the temp-test-ioccc GitHub repo</h4>
<p>Starting on <a href="https://github.com/ioccc-src/winner/commit/2f20ae8451ada03f4601ac727d10e1d8630861a8">2020 Dec
30</a>
edits to the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner
@@ -5542,10 +5542,10 @@ tools and scripts</a>.</li>
contact information via a <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull
request</a>.</li>
<li>Setting up to generate the top level <a href="years.html">years.html</a> file via the
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/bin/gen-years.sh">gen-years.sh</a> tool.</li>
<a href="https://github.com/ioccc-src/winner/blob/master/bin/gen-years.sh">gen-years.sh</a> tool.</li>
<li>Setting up to generate the top level <a href="authors.html">authors.html file</a>, renamed
from <code>winners.html</code>, via the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/bin/gen-authors.sh">gen-authors.sh</a> tool.</li>
<li>Making use of a new and improved <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/ioccc.css">IOCCC CSS</a> for website consistency</li>
from <code>winners.html</code>, via the <a href="https://github.com/ioccc-src/winner/blob/master/bin/gen-authors.sh">gen-authors.sh</a> tool.</li>
<li>Making use of a new and improved <a href="https://github.com/ioccc-src/winner/blob/master/ioccc.css">IOCCC CSS</a> for website consistency</li>
<li>Etc.</li>
</ul>
<div id="great_fork_merge_date">
@@ -5553,7 +5553,7 @@ from <code>winners.html</code>, via the <a href="https://github.com/ioccc-src/te
</div>
<p>As of 2024 Dec 28 <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
repo</a>
there was <a href="https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master">6165+ commits ahead</a>
there was <a href="https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master">6167+ commits ahead</a>
of the <a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>.</p>
<p>On 2024 Dec 28, the temporary repo was merged back into the <a href="https://github.com/ioccc-src/winner">IOCCC winner
repo</a> resulting in many, many substantial improvements
@@ -5722,7 +5722,7 @@ announced in the early years of the IOCCC.</p>
<div id="coda"><h3>Coda</h3>
<p>
<a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Ffaq.html" rel="nofollow">Nu HTML check this web page</a><br>
<a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.ioccc.org%2Ffaq.html" rel="nofollow">Nu HTML check this web page</a><br>
<a href="#top">Jump to top</a> <a href="#content">Jump to Content</a>
</p>
</div>