- User Since
- Jun 8 2015, 2:10 PM (188 w, 6 d)
Fri, Jan 18
Don't use HTTPS for www.codingstandard.com
Thu, Jan 17
I requested merge of updated documentation into 8.0 branch in PR40369.
By the word, I noticed that HTTP was used and replaced it with HTTPS in Contributing.rst. Will be good idea to do the same in other documentation.
I fixed links.
clang-tools-sphinx-docs bot is failing because of:
Wed, Jan 16
Mon, Jan 14
Sun, Jan 13
It'll be worth to mention change in Release Notes (in changes list, in alphabetical order).
Fri, Jan 11
I would suggest to rename contribution to Contributing (see LLVM documentation) and integrations to Integrations.
Thu, Jan 10
Thank you for keeping documentation up-to-date with code!
Wed, Jan 9
It'll be worth to add next suggestion:
Tue, Jan 8
Fri, Jan 4
Wed, Jan 2
Sun, Dec 30
Please mention new check in Release Notes and list of checks. It'll be good idea to used add_new_check.py.
Dec 21 2018
Dec 18 2018
Please run script from D55523 over your changes.
Dec 17 2018
Please close PR25403 after commit.
Dec 13 2018
I think will be good idea to discuss wider application for this script in llvm-dev. If LLVM use Clng-format, why not to use this script?
Dec 12 2018
I think will be good idea to rename script to validate_documentation.py. Or may be lint?
Looks OK for me, but I agree with Jonas, it's better to commit changes made with final version.
Dec 11 2018
Thank you for cleanup effort!
Dec 10 2018
Other common problems which will be great to detect with this script:
By the word, will be good idea to have script which check alphabetical order and use it during build. Sometimes alphabetical order may be violated after merge with trunk.
Thank you for great idea! I think running this script should be part of build, like running Clang-format in Polly.
Thank you for this fix!
Dec 7 2018
Dec 5 2018
Dec 4 2018
Nov 30 2018
Please close PR30233 after committing patch.
Nov 29 2018
Nov 28 2018
Nov 27 2018
Nov 21 2018
Nov 20 2018
Nov 9 2018
Nov 8 2018
Please also add regression test case. Is should also cover standalone function with this variable.
Please mention this check in docs/ReleaseNotes.rst (in alphabetical order).
Nov 7 2018
Please mention new check in Release Notes (in alphabetical order).
C++ Core Guidelines also mentioned similar patterns, so may be this check belongs to bugprone module?