git mv *.hint -> README.md
There is one exception:
$ find . -name '*.hint' -execdir git mv '{}' README.md \;
git statufatal: destination exists, source=1992/albert/albert.hint, destination=1992/albert/README.md
Looking at the two files they differ quite a bit so I've not changed it.
I'll bring this up on GitHub.
This commit is contained in:
1 parent
046692c03e
commit
17ea7fbd9e
155 files changed
No files matched your search
@@ -0,0 +1,32 @@
|
||||
Abusing The Rules:
|
||||
|
||||
Diomidis Spinellis
|
||||
SENA S.A.
|
||||
Kyprou 27
|
||||
GR-152 37 Filothei
|
||||
Greece
|
||||
|
||||
|
||||
Judges' comments:
|
||||
|
||||
To use:
|
||||
make spinellis
|
||||
|
||||
Try:
|
||||
spinellis < spinellis.c
|
||||
|
||||
While code does not abuse the rules, its output surely does!
|
||||
|
||||
P.S. Does the source have any spelling errors?
|
||||
|
||||
|
||||
Selected notes from the author:
|
||||
|
||||
96% of the program lines (631 out of the 658) are comment text rendering
|
||||
the program readable and understandable. With the exception of the
|
||||
two include file names (needed for a warning-free compile) the program
|
||||
passes the standard Unix spell checker without any errors. Checking
|
||||
for spelling errors is considered very important for programs that are
|
||||
so heavily commented. This program is exactly 3217 characters long
|
||||
through judicious use of white space. Rule abuse? Would I _ever_ abuse
|
||||
the rules?
|
||||
Reference in new issue
Block a user