From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pmg-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pmg-devel] applied: [PATCH pmg-api] fix #5966: ruledb: modify header: log action
Date: Mon, 13 Oct 2025 18:36:30 +0200 [thread overview]
Message-ID: <176037338244.1553896.15598682295382546555.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251002143158.25682-1-s.ivanov@proxmox.com>
On Thu, 02 Oct 2025 16:30:57 +0200, Stoiko Ivanov wrote:
> ModField (modify header) is the only action which we currently do not
> log. Originally I skipped it explicitly, expecting this to add too
> many lines on an average system. However it does prevent some
> situations from being debugged correctly (as laid out in #5966), and
> I don't think that the argument of too many log-lines outweighs that.
>
>
> [...]
Applied, thanks!
[1/1] fix #5966: ruledb: modify header: log action
commit: 46eaccb743f35d0a626050953a25cfcd9f75fe65
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
prev parent reply other threads:[~2025-10-13 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 14:30 [pmg-devel] " Stoiko Ivanov
2025-10-13 16:36 ` 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=176037338244.1553896.15598682295382546555.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@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