verbose option misleading
ain opened this issue · comments
Ain Tohvri commented
I think verbose
option in its current form is misleading. I actually expected it to throw out more info on console during the manifest build process not to add a Copyright reference to the header of the manifest file.
I'd separate things a bit and push the behaviour of the current verbose
option to a �richHeaders
for instance or something along the lines. And then verbose
could act as an actual �--verbose
in the *nix world.
Since the features are both harmless and don't break anything, the switch would be possible without legacy support dance?