Age | Commit message (Collapse) | Author |
|
Problem: No LGTM logo in README file.
Solution: Add one. (Bas van Schaik, closes #3305)
|
|
Problem: Header of README file is not nice.
Solution: Move text to the bottom.
|
|
Problem: No Vim logo in README file.
Solution: Add one. (Árni Dagur, closes #3024)
|
|
Update version number and information. Fix a couple of tests.
|
|
Problem: duplicate badge README file.
Solution: Remove one. (Dominique Pelle)
|
|
Problem: Stray + in README file.
Solution: Remove the +. Add a line break.
|
|
Problem: Not easy to find Debian build info.
Solution: Add a badge in the README file. (Dominique Pelle)
|
|
Problem: Typo in link to codecov.io results.
Solution: Remove duplicate https:.
|
|
Problem: No link to codecov.io results.
Solution: Add a badge to the readme file.
|
|
|
|
Problem: README file is not clear about where to get Vim.
Solution: Add links to github, releases and the Windows installer.
(Suggested by Christian Brabandt)
|
|
Problem: README text is slightly outdated.
Solution: Mention the READMEdir directory.
|
|
Problem: No link to Coverity.
Solution: Add Coverity badge in README.
|
|
Problem: The README file contains some outdated information.
Solution: Update the information about supported systems.
|
|
Problem: README file can still be improved
Solution: Add a couple of links. (Christian Brabandt)
|
|
Problem: README file is not optimal.
Solution: Move buttons, update some text. (closes #460)
|
|
Problem: No build and coverage status.
Solution: Add links to the README file. (Christian Brabandt)
|
|
Problem: Not obvious how to contribute.
Solution: Add a remark about CONTRIBUTING.md to README.md
|
|
Problem: The README file doesn't look nice on github.
Solution: Add a markdown version of the README file.
|