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

Log results shouldn't be verbose #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fily55
Copy link

@fily55 fily55 commented Feb 11, 2016

All the stuff before makes sense to be verbose, logging what files that were handled doesn't. For instance, when you run this module you can't see what files have gone up. You can do this by turning on verbose but then you are getting a lot more information you don't need. I feel the files being handled should always be logged.

All the stuff before makes sense to be verbose, logging what files that were handled doesn't. For instance, when you run this module you can't see what files have gone up. You can do this by turning on verbose but then you are getting a lot more information you don't need. I feel the files being handled should always be logged.
@evanplaice
Copy link
Owner

This module follows the linux 'no news is good news' model of logging. Ie when the operation is successful there is no output, to get a detailed log of actions verbose is specified explicitly.

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

Successfully merging this pull request may close these issues.

2 participants