Support borg's --log-level #16
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#16
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Next Borg version will have a --log-level option.
Would be great if this will be implemented.
See: https://github.com/borgbackup/borg/issues/426
Thanks
Mark
Imported from Taiga issue 15 (won't fix). Created on 2015-12-03T10:03:37+0000 by breyer.
Cool, thanks for the heads up. I'm hoping to support this via #14.
Comment on 2015-12-04T06:23:25+0000 by Dan Helfman.
Actually, I take that back. #14 won't get this "for free" because it's not a flag on one of the Borg sub-commands that are wrapped (create/prune/check).
Comment on 2015-12-04T06:25:21+0000 by Dan Helfman.
It looks like Borg never implemented
--log-level
. Do you know if the--critical
/--error
/--warning
/--info
flags are intended to replace that? Would you still want support for those? And if so, what are you trying to accomplish by using these flags and setting Borg's log level? Would it make sense to wrap into borgmatic's existing verbosity levels?Comment on 2017-11-03T05:33:04+0000 by Dan Helfman.
From my view there is no need to support this anymore.
Comment on 2017-11-03T15:37:16+0000 by breyer.
Okay, thanks. Let me know if that changes.
Comment on 2017-11-04T02:57:32+0000 by Dan Helfman.