From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 1/2] use PROXMOX_DEBUG env variable to control loglevel
Date: Fri, 4 Feb 2022 11:22:41 +0100 [thread overview]
Message-ID: <06b9426b-8bba-a281-aad3-4687d318c0af@proxmox.com> (raw)
In-Reply-To: <20220204091221.1781533-1-d.csapak@proxmox.com>
On 04.02.22 10:12, Dominik Csapak wrote:
> so that we can use 'log::debug' to actually log debug messages
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> without this or something similar, we cannot actually see the messages
> from 'log::debug' (and we're using that sometimes)
>
> src/bin/proxmox-backup-proxy.rs | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
>
applied, thanks! This is (for now) unrelated to the better debug-logging
experience I replied at patch 2/2.
prev parent reply other threads:[~2022-02-04 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 9:12 [pbs-devel] " Dominik Csapak
2022-02-04 9:12 ` [pbs-devel] [PATCH proxmox-backup 2/2] traffic-control: add debug log when we found a matching rule Dominik Csapak
2022-02-04 10:05 ` Thomas Lamprecht
2022-02-04 10:09 ` Dominik Csapak
2022-02-04 10:21 ` Thomas Lamprecht
2022-02-04 10:22 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06b9426b-8bba-a281-aad3-4687d318c0af@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox