From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Lukas Wagner" <l.wagner@proxmox.com>, <pbs-devel@lists.proxmox.com>
Subject: Re: [PATCH proxmox-backup] docs: notifications: expand notification queue documentation
Date: Fri, 20 Nov 2026 09:50:02 +0100 [thread overview]
Message-ID: <DMZWQPMGFLRD.10B95OVDCCUAH@proxmox.com> (raw)
In-Reply-To: <20261120084042.94455-1-l.wagner@proxmox.com>
On Fri Nov 20, 2026 at 9:40 AM CET, Lukas Wagner wrote:
> Move the description of queued delivery out of the overview into its
> own section and extend it, mirroring the Proxmox VE documentation.
>
> Point out where to find the logs of the proxmox-backup service in the
> GUI, how interrupted deliveries are retried and that this can lead to
> duplicate notifications for some targets, and describe the queue
> directory, including the naming scheme of queued files and what files
> with a '.broken' suffix mean.
>
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
just as a note, this mirrors the changes from
https://lore.proxmox.com/all/20261119100743.238781-1-l.wagner@proxmox.com/T/#u
prev parent reply other threads:[~2026-11-20 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 8:40 [PATCH proxmox-backup] docs: notifications: expand notification queue documentation Lukas Wagner
2026-11-20 8:50 ` Lukas Wagner [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=DMZWQPMGFLRD.10B95OVDCCUAH@proxmox.com \
--to=l.wagner@proxmox.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