We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently we have the --quiet option in the spec with a question mark behind it. I propose we drop it.
Firstly, having both verbose and quiet as separate entities is confusing,
Secondly, I don't see the use of it. What it currently does is in Module::Build
It's not affecting TAP::Harness, despite that having lots of quietness levels.
I've often wanted a build to be more verbose, but I never wanted it to be more quiet. Maybe because CPAN clients can already make it quiet for me.
The text was updated successfully, but these errors were encountered:
On Sun, Oct 27, 2013 at 05:47:07AM -0700, Leon Timmermans wrote:
+1
Sorry, something went wrong.
I agree. We should only have one of verbose or quiet. I think we should subtly encourage the default to be "quiet" so keeping "verbose" is better.
No branches or pull requests
Currently we have the --quiet option in the spec with a question mark behind it. I propose we drop it.
Firstly, having both verbose and quiet as separate entities is confusing,
Secondly, I don't see the use of it. What it currently does is in Module::Build
It's not affecting TAP::Harness, despite that having lots of quietness levels.
I've often wanted a build to be more verbose, but I never wanted it to be more quiet. Maybe because CPAN clients can already make it quiet for me.
The text was updated successfully, but these errors were encountered: