Reinstate optional pmFetch warnings.
When the warnings were changed to be off by default, the plumbing to allow the previous default to be enabled (-v) was incomplete ... this was causing QA/363 to fail, besides being just wrong.
Reinstate optional pmFetch warnings.
When the warnings were changed to be off by default, the plumbing to allow
the previous default to be enabled (-v) was incomplete ... this was causing
QA/363 to fail, besides being just wrong.