On Mon, Aug 28, 2017 at 03:32:31PM +0200, Ján Tomko wrote:
> On Mon, Aug 28, 2017 at 10:39:15AM +0200, Erik Skultety wrote:
> > Commit 94c465d0 refactored the logging setup phase but introduced an
> > issue, where the daemon ignores verbose mode when there are no outputs
> > defined and the default
On Mon, Aug 28, 2017 at 03:32:31PM +0200, Ján Tomko wrote:
> On Mon, Aug 28, 2017 at 10:39:15AM +0200, Erik Skultety wrote:
> > Commit 94c465d0 refactored the logging setup phase but introduced an
> > issue, where the daemon ignores verbose mode when there are no outputs
> > defined and the default
On Mon, Aug 28, 2017 at 10:39:15AM +0200, Erik Skultety wrote:
Commit 94c465d0 refactored the logging setup phase but introduced an
issue, where the daemon ignores verbose mode when there are no outputs
defined and the default must be used. The problem is that the default
output was determined to
Commit 94c465d0 refactored the logging setup phase but introduced an
issue, where the daemon ignores verbose mode when there are no outputs
defined and the default must be used. The problem is that the default
output was determined too early, thus ignoring the potential '--verbose'
option taking ef