Hello Bruno,
a couple of typo nits:
* Bruno Haible wrote on Sat, Dec 06, 2008 at 12:17:07PM CET:
> ================================ doc/manywarnings.texi
> ========================
> @node manywarnings
> @section manywarnings
>
> The @code{manywarnings} module allows you to enable as many GCC warnings as
> possible for your package. The purpose is to protect against introducing new
> code that triggers warning that weren't already triggered by the existing code
warnings
> base.
> This module is meant to be used by developers who are not very experienced
> regarding the various GCC warning option. In the beginning you will set the
options
> list of undesired warnings (@samp{nw} in the example above) to empty, and
> compile the package with all possible warnings enabled. The GCC option
> @code{-fdiagnostics-show-option}, available in GCC 4.1 or newer, helps
> understanding which warnings is originated from which option. Then you will
s/is //
> go through the list of warnings. You will likely deactivate warnings that
> occur often and don't point to mistakes in the code, by adding them to the
> @samp{nw} variable, then reconfiguring and recompiling. When warnings point
> to real mistakes and bugs in the code, you will of course not disable
> them.
If you like, I can push a patch to fix them.
Cheers,
Ralf
