-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
All messages are output to stderr #7
Comments
Closes jirutka#7 Signed-off-by: fossdd <[email protected]>
Instead of piping to |
This is also a good idea. Nevertheless I opened #17 which should output INFO messages like |
Hmm, after thinking about it. I'm not sure if outputting INFO to stdout makes sense. Often all diagnostic output is written to stderr, including info messages. Maybe a info level variable would make here more sense? @jirutka what do you think about it? |
Closes jirutka#7 Signed-off-by: fossdd <[email protected]>
I noticed all messages, regardless of their importance are redirected to stderr.
This bother me because I've set up a cronjob for apk-autoupdate to run every day like so:
I would expect "Checking available updates..." to be redirected to /dev/null accordingly. Right now, I get an email every day telling me that apk-autoupdate is checking for available updates.
The text was updated successfully, but these errors were encountered: