From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Lucas Barros <lucasbarros.kam@gmail.com>
Subject: applied: [PATCH proxmox] fix #8127: notify: matcher: fix description of match-calendar
Date: Wed, 11 Nov 2026 23:00:47 +0100 [thread overview]
Message-ID: <179443424602.1210260.2950368076107142475.b4-ty@b4> (raw)
In-Reply-To: <20261107223522.23169-1-lucasbarros.kam@gmail.com>
On Sat, 07 Nov 2026 19:35:22 -0300, Lucas Barros wrote:
> The doc comment of the 'match-calendar' property was copied from
> 'match-severity', so the API schema, and with it the CLI help and the
> man page of 'proxmox-backup-manager notification matcher create' and
> 'update', describes it as a list of matched severity levels. The
> option matches the timestamp of a notification against calendar
> entries, though.
>
> [...]
Applied, thanks!
[1/1] fix #8127: notify: matcher: fix description of match-calendar
commit: 0d55affd2b8b2f548f3e169351561c75966ded3f
prev parent reply other threads:[~2026-11-11 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 22:35 [PATCH proxmox] fix #8127: notify: matcher: fix description of match-calendar Lucas Barros
2026-11-09 11:58 ` Christian Ebner
2026-11-11 22:00 ` 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=179443424602.1210260.2950368076107142475.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=lucasbarros.kam@gmail.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