From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs] notifications: fix typos and improve reading flow
Date: Wed, 10 Jan 2024 14:37:04 +0100 [thread overview]
Message-ID: <9a3474b0-3422-4bda-b669-f28067351008@proxmox.com> (raw)
In-Reply-To: <20240110131431.125035-1-c.ebner@proxmox.com>
On 1/10/24 14:14, Christian Ebner wrote:
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
> notifications.adoc | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/notifications.adoc b/notifications.adoc
> index cddb8ca..9be23f8 100644
> --- a/notifications.adoc
> +++ b/notifications.adoc
> @@ -172,11 +172,11 @@ Notification Matchers
> [thumbnail="screenshot/gui-datacenter-notification-matcher.png"]
>
> Notification matchers route notifications to notification targets based
> -on their matching rules. These rules can match of certain properties of
> -a notification, such as the timestamp (`match-calendar`), the severity of
> -the notificaiton (`match-severity`) or metadata fiels (`match-field`).
> -If a matcher matches a notification, all targets configured for the matcher
> -will receive the notification.
> +on their matching rules. These rules can match certain properties of a
> +notification, such as the timestamp (`match-calendar`), the severity of
> +the notificaiton (`match-severity`) or metadata fields (`match-field`).
^
Spotted another typo here
> +If a notification is matched by a matcher, all targets configured for the
> +matcher will receive the notification.
>
> An arbitrary number of matchers can be created, each with with their own
> matching rules and targets to notify.
I guess I wrote that paragraph in a bit of a hurry :)
Thanks!
--
- Lukas
next prev parent reply other threads:[~2024-01-10 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 13:14 Christian Ebner
2024-01-10 13:37 ` Lukas Wagner [this message]
2024-01-10 13:43 ` Christian Ebner
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=9a3474b0-3422-4bda-b669-f28067351008@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pve-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.