Make thanks/complicated/etc. stand out in thanks
As the GitHub bold is rather close in colour to regular text (at least in my admittedly poor vision) I have made the thanks, the complicated and technically challenging stand out more by making them all upper case. I also made the wording (of thanks to me) closer to that of Yusuke but changing in his 'VERY' to 'EXTREMELY': better to have it consistent and some were quite challenging. For entries listed under my name at the top I did not add the word technically as I think that that's implied.
This commit is contained in:
1 parent
8d4ce3b843
commit
b6c42ce86c
1 file changed
+8
-8
+8
-8
@@ -11,20 +11,20 @@ contributed thousands, that we wish to thank.
|
||||
|
||||
We call out the extensive contributions of [Cody Boone
|
||||
Ferguson](https://www.ioccc.org/winners.html#Cody_Boone_Ferguson) who is
|
||||
responsible for most of the improvements and fixes including many **extremely
|
||||
complicated bug fixes** like
|
||||
responsible for most of the improvements and fixes including many **EXTREMELY
|
||||
CHALLENGING bug fixes** like
|
||||
[1988/phillipps](/thanks-for-fixes.md#1988phillipps-readmemd),
|
||||
[2001/anonymous](/thanks-for-fixes.md#2001anonymous-readmemd) and
|
||||
[2004/burley](/thanks-for-fixes.md#2004burley-readmemd), making entries like
|
||||
[1985/sicherman](/thanks-for-fixes.md#1985sicherman-readmemd) and
|
||||
[1986/wall](/thanks-for-fixes.md#1986wall-readmemd) not need `-traditional-cpp`
|
||||
(all **extremely complicated fixes**), fixing entries to work with clang (some
|
||||
being **extremely complicated** like
|
||||
(all **EXTREMELY CHALLENGING**), fixing entries to work with clang (some
|
||||
being **EXTREMELY CHALLENGING** like
|
||||
[1991/dds](/thanks-for-fixes.md#1991dds-readmemd)), porting entries to macOS
|
||||
(some being **very complicated** like
|
||||
(some being **EXTREMELY CHALLENGING** like
|
||||
[1998/schweikh1](/thanks-for-fixes.md#1998schweikh1-readmemd)), fixing code like
|
||||
[2001/herrmann2](/thanks-for-fixes.md#2001herrmann2-readmemd) to work in both
|
||||
32-bit/64-bit which *can be* **very complicated**, providing alternate code
|
||||
32-bit/64-bit which *can be* **VERY CHALLENGING**, providing alternate code
|
||||
where useful/necessary, fixing where possible dead links or removing them,
|
||||
typo/consistency fixes, improving **ALL _Makefiles_** and writing
|
||||
[sgit](https://github.com/xexyl/sgit) that we installed locally to easily run
|
||||
@@ -34,7 +34,7 @@ IOCCC winners and fixing almost all past entries for modern systems!
|
||||
|
||||
[Yusuke Endoh](https://www.ioccc.org/winners.html#Yusuke_Endoh) supplied a
|
||||
number of important bug fixes to a number of past IOCCC winners. Some of those
|
||||
fixes were **very technically challenging** such as
|
||||
fixes were **VERY TECHNICALLY CHALLENGING** such as
|
||||
[1989/robison](/thanks-for-fixes.md#1989robison-readmemd),
|
||||
[1990/cmills](https://github.com/ioccc-src/temp-test-ioccc/blob/master/thanks-for-fixes.md#1990cmills-readmemd),
|
||||
[1992/lush](/thanks-for-fixes.md#1992lush-readmemd) and
|
||||
@@ -45,7 +45,7 @@ A good number of the [past winners of the
|
||||
IOCCC](https://www.ioccc.org/winners.html) tested, identified and helped correct
|
||||
and/or improve the write-ups of fellow IOCCC winners for the year that they won.
|
||||
The list of those past winners is too long to mention: nevertheless the [IOCCC
|
||||
judges](https://www.ioccc.org/judges.html) **very much appreciate** those who
|
||||
judges](https://www.ioccc.org/judges.html) **VERY MUCH APPRECIATE** those who
|
||||
helped improve the presentation of their fellow IOCCC winners.
|
||||
|
||||
|
||||
|
||||
Reference in new issue
Block a user