[PATCH] D61850: Removed superfluous and slightly annoying newlines in run-clang-tidy's output.

svenpanne added a comment. I think `ninja clang-test-tools` is the right target here, and it is happy with the change, which is not very surprising: AFAICT, there is just a single, very simple check for `run-clang-tidy.py`. Anyway, my manual testing with and without `-quiet` shows no problems,

[PATCH] D61849: Do not list enabled checks when -quiet is given to run-clang-tidy.

svenpanne added a comment. Thanks for the review. How will the patch be merged? According to https://llvm.org/docs/Phabricator.html#committing-a-change, someone else has to do it for me, because AFAICT, I have no commit rights. As I said: I'm still in the process of learning the workflow here..

[PATCH] D61850: Removed superfluous and slightly annoying newlines in run-clang-tidy's output.

svenpanne added a comment. In D61850#1500298 , @JonasToth wrote: > [...] please ensure that e.g. clang-analyzer-* output looks proper as well > and `-quiet` does, too. OK, are there any (unit) tests which I should run? If yes, how exactly? I have a suc

[PATCH] D61850: Removed superfluous and slightly annoying newlines in run-clang-tidy's output.

svenpanne created this revision. svenpanne added a reviewer: alexfh. Herald added a project: clang. Herald added a subscriber: cfe-commits. The output of clang-tidy itself already has enough newlines, so the resulting output is more in line with the usual compiler output. Repository: rCTE Cla

[PATCH] D61849: Do not list enabled checks when -quiet is given to clang-tidy.

svenpanne created this revision. svenpanne added a reviewer: alexfh. Herald added a project: clang. Herald added a subscriber: cfe-commits. When clang-tidy is given the -quiet flag, do not output the potentially hundreds of enabled check names at the beginning. Repository: rCTE Clang Tools Ex