Lines Matching full:warnings

30 Addressing warnings
34 warnings.  When you have that many, you might as well have none at all;
36 ones.  For this reason, eliminating warnings is one of the highest-priority
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
44 problem; making those warnings go away requires understanding the problem
46 warnings should probably not say "fix a warning" in the changelog title;
49 Another important point is that documentation warnings are often created by
51 maintainer appreciates being copied on fixes for these warnings, the
55 For example, in a documentation build I grabbed a pair of warnings nearly
89   resulting in these doc-build warnings:
137 times, but it's highly important.  If we can actually eliminate warnings
141 In addition to warnings from the regular documentation build, you can also