I like the idea of having an optional warning for this,
with the default being no warning, but is it wise
to introduce a new level of verbosity for this?  It'd
be simpler if ordinary -v enabled this new warning,
as it does the other warnings, and I'm wondering why
the simpler route wasn't taken.

Reply via email to