Skip to content
New issue

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

verbose option misleading #39

Open
ain opened this issue Jan 15, 2014 · 0 comments
Open

verbose option misleading #39

ain opened this issue Jan 15, 2014 · 0 comments

Comments

@ain
Copy link

ain commented Jan 15, 2014

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant