From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Lukas Wagner <l.wagner@proxmox.com>,
Wolfgang Bugmiller <w.bumiller@proxmox.com>
Subject: [pve-devel] [PATCH cluster] notify: use renamed Proxmox::RS::Notify
Date: Mon, 24 Jul 2023 13:26:58 +0200 [thread overview]
Message-ID: <20230724112659.524038-2-l.wagner@proxmox.com> (raw)
In-Reply-To: <20230724112659.524038-1-l.wagner@proxmox.com>
Suggested-by: Wolfgang Bugmiller <w.bumiller@proxmox.com>
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
src/PVE/Notify.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/PVE/Notify.pm b/src/PVE/Notify.pm
index 48ef772..0464362 100644
--- a/src/PVE/Notify.pm
+++ b/src/PVE/Notify.pm
@@ -4,7 +4,7 @@ use strict;
use warnings;
use PVE::Cluster qw(cfs_register_file cfs_read_file cfs_lock_file cfs_write_file);
-use PVE::RS::Notify;
+use Proxmox::RS::Notify;
cfs_register_file(
'notifications.cfg',
@@ -46,7 +46,7 @@ sub read_config {
my $config = cfs_read_file('notifications.cfg');
my $priv_config = cfs_read_file('priv/notifications.cfg');
- my $notification_config = PVE::RS::Notify->parse_config($config, $priv_config);
+ my $notification_config = Proxmox::RS::Notify->parse_config($config, $priv_config);
eval {
# This target should always be available...
--
2.39.2
next prev parent reply other threads:[~2023-07-24 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 11:26 [pve-devel] [PATCH proxmox-perl-rs] notify: rename PVE::RS::Notify to Proxmox::RS::Notify Lukas Wagner
2023-07-24 11:26 ` Lukas Wagner [this message]
2023-07-24 13:02 ` [pve-devel] partially-applied: [PATCH cluster] notify: use renamed Proxmox::RS::Notify Wolfgang Bumiller
2023-07-24 11:26 ` [pve-devel] [PATCH manager] vzdump: use <name> as a convention for virtual endpoints/groups Lukas Wagner
2023-07-26 9:55 ` Lukas Wagner
2023-07-24 12:40 ` [pve-devel] partially-applied: [PATCH proxmox-perl-rs] notify: rename PVE::RS::Notify to Proxmox::RS::Notify Wolfgang Bumiller
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=20230724112659.524038-2-l.wagner@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@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