updated FAQ 1.2 with detailed repo history

The "FAQ 1.2: What is the history of the IOCCC web site"
entry with detailed information about GitHub repo history.

faq.html

@@ -601,41 +601,168 @@ details about these bzip2 compressed tarballs.</p>
 <p><strong>XXX</strong>: Change the references to
 <em>temp-test-ioccc</em> to <em>winners</em> when these fixes are
 merged.</p>
-<h4 id="dec-29-repo-fork">2022 Dec 29 repo fork</h4>
-<p>On 2022 Dec 29, the <a
-href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>, from
-which the <a
+<h4 id="dec-29-official-ioccc-winner-repo">2022 Dec 29 Official IOCCC
+winner repo</h4>
+<p>The <a href="https://github.com/ioccc-src/winner">Official IOCCC
+winner repo</a> was <a
+href="https://github.com/ioccc-src/winner/commit/28efc67f5dd692a3544708bf7fa26286adb82dfb">created
+on 2020 Dec 29</a>.</p>
+<h4 id="dec-30-ioccc-content-uploaded-to-github">2020 Dec 30 IOCCC
+content uploaded to GitHub</h4>
+<p>An <a href="https://www.ioccc.org/judges.html">IOCCC judge</a> formed
+a local directory <a href="https://git-scm.com">git</a> repo on
+<strong>Tue Dec 29 23:48:30 2020 -0800</strong> via <a
+href="https://github.com/ioccc-src/winner/commit/28efc67f5dd692a3544708bf7fa26286adb82dfb">commit
+28efc67f5dd692a3544708bf7fa26286adb82dfb</a> and then on <strong>Wed Dec
+30 16:57:03 2020 -0800</strong> added a preview of 1984-2019 via <a
+href="https://github.com/ioccc-src/winner/commit/c0663537cb88d39b74285a930ff1a668c6d5968b">commit
+c0663537cb88d39b74285a930ff1a668c6d5968b</a>.</p>
+<p>On <a
+href="https://github.com/ioccc-src/winner/commit/c0663537cb88d39b74285a930ff1a668c6d5968b">2020
+Dec 30</a> the <a
 href="https://web.archive.org/web/20221231001721/https://www.ioccc.org/">official
-IOCCC web site of 2022 Dec 29</a> was generated, was forked into a
-temporary repo where it underwent several thousand changes and important
-improvements such as:</p>
+IOCCC web site of 2022 Dec 29</a> was uploaded into the <a
+href="https://github.com/ioccc-src/winner">Official IOCCC winner
+repo</a>.</p>
+<h4 id="ioccc-winning-entries-released-using-git-via-github">2020 IOCCC
+winning entries released using git via GitHub</h4>
+<p>The <a
+href="https://github.com/ioccc-src/winner/commit/9d61fc0fb4a3245afb1435458cfb597fad0e8e6a">winning
+entries of the 2020 IOCCC</a>, after a far too long of a delay (due in
+part to a <a
+href="https://github.com/ioccc-src/winner/commit/c94fc84c35dc83e3eb9900720b95917a15c27afe">former
+IOCCC judge who resignation was noted on 2021 Jan 04</a>) from their
+initial <a
+href="https://web.archive.org/web/20200726232505/http://www.ioccc.org:80/index.html">2020
+Jul 25 announcement</a>, the <a
+href="https://www.ioccc.org/years.html#2020">2020 IOCCC winning
+entries</a> were added by an <a
+href="https://www.ioccc.org/judges.html">IOCCC judge</a> to their local
+<a href="https://git-scm.com">git</a> repository, then were merged into
+the <a
+href="https://github.com/ioccc-src/winner/commit/b1638ff0012964d79ab1c44aa815d3f824f35b6c">Official
+IOCCC winner repo on 2020 Dec 31</a>.</p>
+<p>These <a href="https://www.ioccc.org/years.html#2020">2020 IOCCC
+winning entries</a>, 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">2021
+Jan 02</a> snapshot, 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>
+<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
+repo</a> began.</p>
+<p>The local <a href="https://git-scm.com">git</a> repository of an <a
+href="https://www.ioccc.org/judges.html">IOCCC judge</a> was edited
+starting <a
+href="https://github.com/ioccc-src/winner/commit/c0663537cb88d39b74285a930ff1a668c6d5968b">Wed
+Dec 30 16:57:03 2020 -0800</a> and was occasionally committed to the <a
+href="https://github.com/ioccc-src/winner">Official IOCCC winner
+repo</a>.</p>
+<p>The <a href="https://github.com/ioccc-src/winner/pull/2">first
+accepted pull request</a> to the <a
+href="https://github.com/ioccc-src/winner">Official IOCCC winner
+repo</a> was made by <a href="https://github.com/mame">Yusuke Endoh</a>
+on <a
+href="https://github.com/ioccc-src/winner/commit/84c62c4cbf56ac1351ea91e5019f51103615fda2">2021
+Jan 5</a>.</p>
+<p>Between <a
+href="https://github.com/ioccc-src/winner/commit/c0663537cb88d39b74285a930ff1a668c6d5968b">Wed
+Dec 30 16:57:03 2020 -0800</a> and <a
+href="https://github.com/ioccc-src/winner/commit/098a3e7e04d43e480ecc4b5482c83274e1434002">Sat
+Jan 29 21:56:53 2022 -0800</a>, an <a
+href="https://www.ioccc.org/judges.html">IOCCC judge</a> made edits to
+their local repository with occasional the <a
+href="https://github.com/ioccc-src/winner">Official IOCCC winner
+repo</a> and the <a href="https://www.ioccc.org/index.html">Official
+www.ioccc.org web site</a>. After that time and until the <strong>Great
+Fork Merge</strong>, only a very few changes were made to the <a
+href="https://github.com/ioccc-src/winner">Official IOCCC winner
+repo</a> and the <a href="https://www.ioccc.org/index.html">Official
+www.ioccc.org web site</a> most of which were news updates.</p>
+<p>While the <a
+href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
+repo</a> has history going back to <a
+href="https://github.com/ioccc-src/temp-test-ioccc/commit/28efc67f5dd692a3544708bf7fa26286adb82dfb">2020
+Dec 29</a>, the repo was forked on <strong>Sun Sep 18 17:30:00 2022
+-0700</strong>. The first push into the temp-test-ioccc repo occurred on
+<a
+href="https://github.com/ioccc-src/temp-test-ioccc/commit/edbc3089e1b755d85a020af7975bbc7df3737a5f">Sun
+Sep 18 11:15:49 2022 -0700</a>. As this same time, the <a
+href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web
+site</a> went live.</p>
+<p>Edits were made by an <a
+href="https://www.ioccc.org/judges.html">IOCCC judge</a> to their local
+<a href="https://git-scm.com">git</a> repository, were pushed onto the
+<a
+href="https://github.com/ioccc-src/temp-test-ioccc/commit/2f20ae8451ada03f4601ac727d10e1d8630861a8">temp-test-ioccc
+repo</a> and to the <a
+href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web
+site</a>.</p>
+<p>The <a
+href="https://github.com/ioccc-src/temp-test-ioccc/pull/15">first
+accepted pull request</a> made directly to the <a
+href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
+repo</a> on <a
+href="https://github.com/ioccc-src/temp-test-ioccc/commit/11bb36ac8ce790f32a9a3e5d2131ee12820fb8ec">Wed
+Feb 22 05:44:55 2023 -0800</a></p>
+<p>A <a
+href="https://github.com/ioccc-src/temp-test-ioccc/discussions/1918">decision
+was made by the IOCCC</a> to mostly use frequent commits to individual
+components of the IOCCC, rather than to use occasional site wide massive
+updates in order to improve the tractability of changes made to
+components of the IOCCC such as IOCCC entries. Although occasionally
+site wide updated were performed in order to address an issue common to
+many IOCCC entries. And while some people prefer infrequent updates to a
+repo the <a href="https://www.ioccc.org/judges.html">IOCCC judges</a>
+believe the ability to trace changes with commit messages is
+important.</p>
+<p>Changes to the IOCCC content included things such as:</p>
 <ul>
 <li>Moving IOCCC entries into their own separate directories</li>
+<li>Establishing a detailed manifest for an IOCCC winning entries</li>
 <li>Fixing lots and lots of typos</li>
 <li>Fixing Makefiles and code to allow for nearly all winning entries to
-be compiled and work on modern systems</li>
+be compiled modern systems</li>
+<li>Fixing Makefiles and code to allow for nearly all winning entries to
+run modern systems</li>
 <li>Reworking the Makefiles to use a consistent set of rules</li>
 <li>Reworking the Makefiles specific to the gcc and clang C
 compilers</li>
 <li>Replacing the various hint files with a index.html markdown that is
 more consistent across IOCCC years</li>
+<li>Generating HTML content from markdown files and JSON data files via
+a set to tools and scripts</li>
 <li>Setting up a system whereby authors of IOCCC entries may update
 their own contact information via a GitHub pull request</li>
 <li>Setting up to generate the top level years.html file via a tool</li>
 <li>Setting up to generate the top level authors.html file via a
 tool</li>
+<li>Making use of an new and improved IOCCC CSS for web site
+consistency</li>
 <li>etc.</li>
 </ul>
-<h4 id="yy-mm-dd-the-great-fork-merge">20yy mm dd the great fork
-merge</h4>
-<p>On 20yy mm dd, the temporary repo was merged back into the <a
+<h4 id="y-mm-dd-the-great-fork-merge">202y mm dd The Great Fork
+Merge</h4>
+<p>As of 2024 Mar 5 <a
+href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
+repo</a> there were <a
+href="https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master">4513
+commits ahead</a> of the <a
+href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>.</p>
+<p>On 202y mm dd, the temporary repo was merged back into the <a
 href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>
 resulting in substantial improvements to the <a
 href="https://www.ioccc.org">official IOCCC web site</a>.</p>
 <p><strong>XXX</strong>: Fill in the date when the pull request happens
 including the size of the pull request and/or number of changes that
-went into the pull request. We call this the <strong>great fork
-merge</strong>.</p>
+went into the pull request. We call this the <strong>Great Fork
+Merge</strong>.</p>
 <h3
 id="faq-1.3-how-has-the-ioccc-size-limit-rule-changed-over-the-years"><a name="faq1_3"></a><a name="size_rule"></a>FAQ
 1.3: How has the IOCCC size limit rule changed over the years?</h3>