summaryrefslogtreecommitdiff
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
* Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* Update http to httpsDusta2018-06-251-2/+2
|
* add build status badgeAnatol Belski2016-12-161-0/+1
|
* Fix typoxiabeifeng2016-06-041-1/+1
|
* Use svg instead of png to get better image qualityPeter Dave Hello2015-01-251-1/+1
|
* Link to more readmesHannes Magnusson2013-10-271-1/+10
|
* Add preliminary README.md for githubDavid Soria Parra2012-06-031-0/+30
Github uses a special markdown syntax and display the content of the README formatted on the front page of the repo. This readme contains information for github users.