Bug#901991: marked as done (LogLevel vs log_level vs --log-level)

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2018 23:29:44 +0200
with message-id <0d833c39-21ed-3789-3b30-b1c0b00e5e4b at debian.org>
and subject line Re: Bug#901991: LogLevel vs log_level vs --log-level
has caused the Debian Bug report #901991,
regarding LogLevel vs log_level vs --log-level
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
901991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901991
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Harald Dunkel <harald.dunkel at aixigo.de>
Subject: LogLevel vs log_level vs --log-level
Date: Thu, 21 Jun 2018 07:36:47 +0200
Size: 2504
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180627/78945a2b/attachment-0004.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#901991: LogLevel vs log_level vs --log-level
Date: Wed, 27 Jun 2018 23:29:44 +0200
Size: 7514
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180627/78945a2b/attachment-0005.mht>