fix RTFS guideline :-)
This commit is contained in:
1 parent
4256b02327
commit
21798a1005
3 files changed
+4
-4
No files matched your search
@@ -1300,7 +1300,7 @@ of the number of the kernel disk pack of one of the judge’s <a href="https://e
|
|||||||
<p>There may or may not be fewer than 2^7+1 reasons why these <a href="guidelines.html">IOCCC
|
<p>There may or may not be fewer than 2^7+1 reasons why these <a href="guidelines.html">IOCCC
|
||||||
guidelines</a> seem obfuscated.</p>
|
guidelines</a> seem obfuscated.</p>
|
||||||
<p>Excessively “<em>dotty”</em> use of the <code>chksubmit(1)</code> or <code>chkentry(1)</code> commands suggests that
|
<p>Excessively “<em>dotty”</em> use of the <code>chksubmit(1)</code> or <code>chkentry(1)</code> commands suggests that
|
||||||
either you like silly things, or that you”<em>RTFS”</em> with some level of care.</p>
|
either you like silly things, or that you ”<em>RTFS</em>” with some level of care.</p>
|
||||||
<p>Some people might question what actually constitutes a valid JSON file, given
|
<p>Some people might question what actually constitutes a valid JSON file, given
|
||||||
the state of the “<em>so-called</em>” JSON spec.. :-)</p>
|
the state of the “<em>so-called</em>” JSON spec.. :-)</p>
|
||||||
<p>We prefer programs that do not require a fish license: crayons and
|
<p>We prefer programs that do not require a fish license: crayons and
|
||||||
|
|||||||
+1
-1
@@ -1124,7 +1124,7 @@ There may or may not be fewer than 2^7+1 reasons why these [IOCCC
|
|||||||
guidelines](guidelines.html) seem obfuscated.
|
guidelines](guidelines.html) seem obfuscated.
|
||||||
|
|
||||||
Excessively "_dotty"_ use of the `chksubmit(1)` or `chkentry(1)` commands suggests that
|
Excessively "_dotty"_ use of the `chksubmit(1)` or `chkentry(1)` commands suggests that
|
||||||
either you like silly things, or that you "_RTFS"_ with some level of care.
|
either you like silly things, or that you\ "_RTFS_" with some level of care.
|
||||||
|
|
||||||
Some people might question what actually constitutes a valid JSON file, given
|
Some people might question what actually constitutes a valid JSON file, given
|
||||||
the state of the "_so-called_" JSON spec.. :-)
|
the state of the "_so-called_" JSON spec.. :-)
|
||||||
|
|||||||
+2
-2
@@ -16826,11 +16826,11 @@
|
|||||||
</url>
|
</url>
|
||||||
<url>
|
<url>
|
||||||
<loc>https://www.ioccc.org/next/guidelines.html</loc>
|
<loc>https://www.ioccc.org/next/guidelines.html</loc>
|
||||||
<lastmod>2025-11-30T01:19:21+00:00</lastmod>
|
<lastmod>2025-11-30T06:53:29+00:00</lastmod>
|
||||||
</url>
|
</url>
|
||||||
<url>
|
<url>
|
||||||
<loc>https://www.ioccc.org/next/guidelines.md</loc>
|
<loc>https://www.ioccc.org/next/guidelines.md</loc>
|
||||||
<lastmod>2025-11-30T01:18:54+00:00</lastmod>
|
<lastmod>2025-11-30T06:53:23+00:00</lastmod>
|
||||||
</url>
|
</url>
|
||||||
<url>
|
<url>
|
||||||
<loc>https://www.ioccc.org/next/index.html</loc>
|
<loc>https://www.ioccc.org/next/index.html</loc>
|
||||||
|
|||||||
Reference in new issue
Block a user