Verbosity is inconsistent between text and binary protocols

[GoogleCodeExporter]

From the list:

With version 1.4.1, when setting verbose mode to 1, with ASCII
clients, it almost outputs nothing while with binary clients, all SET/
GET/... operations are outputted, making this mode unsuitable for
anything else than pure test.
My understanding (or said another way, the behaviour in 1.2.* ;-) )
was that -v option would be compatible with production configuration
for people who still like to have some info if things go wrong (there
are still -vv and -vvv for deep debugging !). Is it definitely not the
case anymore with 1.4.* version? Or is it planned to transform a few
"if (settings.verbose)" in "if (settings.verbose>1)" to only log
abnormal conditions information for verbosity 1 ?

Original issue reported on code.google.com by dsalli...@gmail.com on 22 Sep 2009 at 3:06

[GoogleCodeExporter]

I'd be glad to take on this bug.

Original comment by CaptTo...@gmail.com on 22 Sep 2009 at 3:16

[GoogleCodeExporter]

Dormando fixed in 783da601f99ba608273350d8566c43ab34a3af97

Original comment by dsalli...@gmail.com on 8 Oct 2009 at 2:32

• Changed state: Fixed