-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Too many warnings! #896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too many warnings! #896
Conversation
I see that you changed the title this time... :-) |
I suggest to make smaller pull requests which focus on closely related problems. That would make reviewing and pulling them much easier. Example: Make a pull request for all changes related to For that example, the |
75243f9
to
edc5f07
Compare
You mean like the diminutive "Use POSIX data types and macros" with only 21 commits and 243 files changed? Yeah, at first I thought |
I don't expect that pull request #878 will be applied like that, but yes, it consists of smaller commits which cover limited modifications and which can be applied individually. |
Even individual #878 commits are way bigger than this whole pull request (or at least the one I randomly picked). Feel free to split it up further as you like, but I don't see the point: it's already themed by kind of warning, and the larger of the two commits is only +32/−24. |
Rebased. TODO: warnings from "make training" |
@rfschtkt: there is merge a conflict in api/pdfrenderer.cpp. Can you fix it? |
Warnings from "make training". Rebased. The remedies were not always obvious, so comments welcome. |
Important warnings warrant attention because they may indicate real problems.
Unimportant warnings warrant attention because they obscure the important warnings.
Unfortunately for me the nicest example of the former category, where I also immediately had a solution, was already fixed independently...
This replaces earlier attempts, now up to date, on its own branch, and with some revisions.