From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 18FAB1FF0B3 for ; Wed, 11 Nov 2026 23:02:50 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9BB1B21622; Wed, 11 Nov 2026 23:02:49 +0100 (CET) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Lucas Barros Subject: applied: [PATCH proxmox] fix #8127: notify: matcher: fix description of match-calendar Date: Wed, 11 Nov 2026 23:00:47 +0100 Message-ID: <179443424602.1210260.2950368076107142475.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261107223522.23169-1-lucasbarros.kam@gmail.com> References: <20261107223522.23169-1-lucasbarros.kam@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794434564874 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.266 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: SP64COLHMMHUHYU5FEF3F2JMGARF4FGI X-Message-ID-Hash: SP64COLHMMHUHYU5FEF3F2JMGARF4FGI X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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