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

Silence logger messages #2415

Closed
vjon opened this issue Apr 13, 2017 · 2 comments
Closed

Silence logger messages #2415

vjon opened this issue Apr 13, 2017 · 2 comments
Labels

Comments

@vjon
Copy link

vjon commented Apr 13, 2017

This is a generalization of jborg/attic#386

I'm curious as to whether anybody here would find an additional log_level to silence all logging particularly useful? In the example use case presented in the original attic issue, the Repository {} already exists error message could be silenced using --critical. Of course, this would also work to silence the majority of error messages for usage in automated backup scripts/etc.

So then the question becomes whether the --critical flag is sufficient, or whether a --quiet flag would provide enough added benefit to justify inclusion?

@ThomasWaldmann
Copy link
Member

I don't think serious log messages should be silenced.

For the specific case of borg init on an existing repo:

just don't run borg init if the repo exists, problem solved.

@enkore
Copy link
Contributor

enkore commented May 1, 2017

See #271

@enkore enkore closed this as completed May 1, 2017
@enkore enkore added the wontfix label May 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants