IMPORTANT NOTE: The IOCCC submit server is only ready for submissions ONLY WHEN THE CONTEST IS open.
-See current status of the IOCCC for details on the contest status. -IMPORTANT NOTE: When the contest is closed, the +
See current status of the IOCCC for details on the contest status.
+IMPORTANT NOTE: When the contest is closed, the IOCCC submit server -may be offline and unreachable as a web site.
+might be offline and unreachable as a website.NOTE: if you do need to update a submission, you might find the FAQ on “how to not have to re-enter information more than once” useful.
@@ -742,7 +742,7 @@ code, your Makefile, your remarks, any other data files you wish to provide (up to a maximum, including the mandatory files, defined in limit_ioccc.h asMAX_FILE_COUNT) and other information about your submission,
-information about the author (or authors), and then runs a lot of tests before (if
+information about the author (or authors), and then it runs a lot of tests before (if
all is OK) forming your tarball. After this is done it will additionally run the
txzchk(1) tool (which runs the fnamchk(1) tool) on the submission tarball.
The tool chkentry(1) will also be run, before creating the tarball. See the
@@ -823,7 +823,7 @@ be the subdirectory with your submission’s files.
The mkiocccentry(1) tool will ask you for information about your
submission as well as author details (that will only be looked at if the
submission wins), run some tests and run a number of other tools, as briefly
-mentioned, and as described in the
+mentioned earlier, and as described in the
“finer details” section.
See also the mkiocccentry repo FAQ @@ -846,8 +846,7 @@ or later SUS.
We recommend starting with the sample -Makefile +
We recommend starting with the sample
(renamed as Makefile of course) as a starting point for your
entry’s Makefile:
Jump to: top
@@ -1114,7 +1113,7 @@ over there. (although we hope you consider asking it in public for the benefit of others), then use the How to contact the IOCCC information to ask a private question. -IMPORTANT: When you ask your question (in public or as a private question) +
IMPORTANT NOTE: When you ask your question (in public or as a private question) PLEASE try to NOT discuss detailed information about any pending submission. Try to ask for question in a more generic way as this will help others with a similar question and this will not give away what you might be doing diff --git a/faq.md b/faq.md index 33e044f61..7e8caf24b 100644 --- a/faq.md +++ b/faq.md @@ -347,9 +347,10 @@ is only ready for submissions **ONLY WHEN THE CONTEST IS [open](status.html#open)**. See [current status of the IOCCC](status.html) for details on the contest status. + **IMPORTANT NOTE**: When the contest is [closed](status.html#closed), the [IOCCC submit server](https://submit.ioccc.org) -may be offline and unreachable as a web site. +might be offline and unreachable as a website. **NOTE**: if you do need to update a submission, you might find the FAQ on "[how to not have to re-enter information more than once](#answers_file)" @@ -392,7 +393,7 @@ code, your Makefile, your remarks, any other data files you wish to provide (up to a maximum, including the mandatory files, defined in [limit_ioccc.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h) as `MAX_FILE_COUNT`) and other information about your submission, -information about the author (or authors), and then runs a lot of tests before (if +information about the author (or authors), and then it runs a lot of tests before (if all is OK) forming your tarball. After this is done it will additionally run the `txzchk(1)` tool (which runs the `fnamchk(1)` tool) on the submission tarball. The tool `chkentry(1)` will also be run, before creating the tarball. See the @@ -506,7 +507,7 @@ be the _subdirectory_ with your submission's files**. The `mkiocccentry(1)` tool will ask you for information about your submission _as well as author details_ (that will only be looked at if the submission wins), run some tests and run a number of other tools, as briefly -mentioned, and as described in the +mentioned earlier, and as described in the "[finer details](#mkiocccentry_details)" section. See also the @@ -538,8 +539,7 @@ Jump to: [top](#) -We recommend starting with the [sample -Makefile](next/Makefile.example) +We recommend starting with the sample (renamed as `Makefile` of course) as a starting point for your entry's `Makefile`: @@ -649,8 +649,8 @@ it, not very obfuscated entries have a minuscule chance to win (although [2000/tomx](2000/tomx/index.html) is a notable counterexample). - mentioning your name or any identifying information in the remark section (or in the C code for that matter) - we like to be unbiased during the judging -rounds; we look at the author name only if an entry wins. See the guidelines if -this is not clear! +rounds; we look at the author name only if an entry wins. See the +[guidelines](next/guidelines.html) **AND** [rules](next/rules.html) if this is not clear! - leaving the remark section empty. Jump to: [top](#) @@ -880,7 +880,7 @@ If you do not feel, for some reason, comfortable asking your question in public then use the [How to contact the IOCCC](contact.html) information to ask a private question. -**IMPORTANT**: When you ask your question (in public or as a private question) +**IMPORTANT NOTE**: When you ask your question (in public or as a private question) **PLEASE** try to **NOT** discuss detailed information about any pending submission. Try to ask for question in a more generic way as this will help others with a similar question and this will not **give away** what you might be doing diff --git a/inc/index.html b/inc/index.html index a3b888d26..051adfe04 100644 --- a/inc/index.html +++ b/inc/index.html @@ -150,8 +150,8 @@
@@ -318,8 +318,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC diff --git a/inc/topbar.default.html b/inc/topbar.default.html index fc57b8015..188951113 100644 --- a/inc/topbar.default.html +++ b/inc/topbar.default.html @@ -106,8 +106,8 @@ @@ -274,8 +274,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC diff --git a/index.html b/index.html index bd2690631..5d48b027a 100644 --- a/index.html +++ b/index.html @@ -150,8 +150,8 @@ @@ -318,8 +318,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC diff --git a/judges.html b/judges.html index 109b51f48..fd3c72111 100644 --- a/judges.html +++ b/judges.html @@ -150,8 +150,8 @@ @@ -318,8 +318,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC diff --git a/license.html b/license.html index 4871abd6a..fbfdc36fb 100644 --- a/license.html +++ b/license.html @@ -150,8 +150,8 @@ @@ -318,8 +318,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC diff --git a/location.html b/location.html index 619f26fe0..7319f26b3 100644 --- a/location.html +++ b/location.html @@ -150,8 +150,8 @@ @@ -318,8 +318,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC diff --git a/markdown.html b/markdown.html index 8a9a6e8df..98cd1089c 100644 --- a/markdown.html +++ b/markdown.html @@ -150,8 +150,8 @@ @@ -318,8 +318,8 @@ Frequently Asked Questions - - How to enter + + Enter the IOCCC @@ -431,7 +431,7 @@IMPORTANT: Be sure to read the IOCCC rules and IOCCC guidelines.
@@ -809,7 +809,10 @@ italic. **_this text is bold italic_**or:
_**this text is bold italic**_BTW: the astute reader might notice that some cases of * for italic might
+have slipped through. We do ask you, however, to please observe this rule, as
+best you can.
+
IMPORTANT: Be SURE to read the IOCCC rules.
Jump to: top
@@ -511,6 +511,11 @@ The submit URL should be active on or slightly before 2024-MMM-DD HH:MM: XXX - date/time is TBD - XXX + +Jump to: top
NOTE: If you prefer to NOT click links in email, simply copy that -URL from your “Subscription consent email” and paste it into your browser. The
+URL from your “Subscription consent email” and paste it into your browser.While the contest is PENDING, you may register for contest, however you will NOT receive an email message containing your IOCCC submit server -Username and Initial Password until the IOCCC is open.
+Username and Initial Password until the IOCCC is open.While the contest is OPEN, you may register for the contest. Once you are registered AND diff --git a/next/register.md b/next/register.md index dd1b7b74d..4fb1e3c95 100644 --- a/next/register.md +++ b/next/register.md @@ -67,7 +67,7 @@ Click on that link. The email might look the below: width=590 height=253> **NOTE**: If you prefer to **NOT** click links in email, simply copy that -URL from your "Subscription consent email" and paste it into your browser. The +URL from your "Subscription consent email" and paste it into your browser.
Where useful he added some notes to the Makefiles during compilation to let one
know of certain problems or features that matter for instance having to disable
the optimiser or in one case enabling -g.
Also, rather than check $(CC) for exact matches of gcc or clang it now is
-that if $(CC) contains gcc or contains clang then the specific actions
+
Also, rather than check ${CC} for exact matches of gcc or clang it now is
+that if ${CC} contains gcc or contains clang then the specific actions
related to the specific compiler will be done (priority is gcc then clang). This
is useful because it’s not guaranteed that the compiler names for gcc or
clang will be exactly that; in macOS for instance it can happen that they are
@@ -5088,19 +5088,13 @@ optimiser to fix an entry, sometimes causing other problems that also had to be
fixed, a good example being 1986/marshall (see the
compilers.html for the amusing details and all that
had to be done to fix it).
There was a ‘problem’ where ${MAKE} was $(MAKE): this doesn’t break anything
-but it is inconsistent with the rest of the ${foo} tools even if by tradition
-it is $(MAKE).
Cody also added missing variables like BASH and PDFLATEX to the
var.mk file and removed another that was deemed problematic or
undesired. Other variable names had typos in them.
In at least one case, like the top level Makefile, where raw commands that are in var.mk were used, Cody updated them to use the variables.
-A comment was missing for the diff_alt_orig rule in all the Makefiles and
-this, along with many other fixes and changes to the Makefiles were made by
-Cody’s sgit tool but many other changes he did
-manually.
Some comments were fixed or added where it was deemed useful.
Jump to: top
Some of these fixes were done with his sgit -tool as well but the vast majority were done -manually.
Jump to: top
README.md files (that we use to ge
run sed(1) on specified files under git that we sometimes use to edit the
website, greatly improved the manifests and checked that the generated html
files look good and are presentable, suggested CSS rules for
-image responsiveness (and other CSS improvements) and he greatly improved the FAQ.
+image responsiveness (and made other CSS improvements) and he greatly improved the FAQ.
Cody also wrote some of the website scripts, improved and bug fixed others, co-developed the JSON parser and tools with us, as we now make extensive use of JSON, and helped test and fix the submit server and mailing list for IOCCC28 and beyond.
THANK YOU VERY MUCH for your extensive efforts in helping improve the IOCCC -presentation of past IOCCC entries, fixing almost all entries that no +presentation of past IOCCC entries, fixing many entries that no longer worked and getting the IOCCC where it is today!
Jump to: top