From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: [pve-devel] superseded: [PATCH docs] notifications: adapt to latest notification system UI changes
Date: Fri, 25 Jul 2025 10:23:15 +0200 [thread overview]
Message-ID: <DBKZP2NMCSHS.N7ZASEZG5HIT@proxmox.com> (raw)
In-Reply-To: <20250723095414.112736-1-l.wagner@proxmox.com>
v2:
https://lore.proxmox.com/pve-devel/20250725082046.51199-1-l.wagner@proxmox.com/T/#u
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-25 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 9:53 [pve-devel] " Lukas Wagner
2025-07-23 12:17 ` Michael Köppl
2025-07-23 12:29 ` Lukas Wagner
2025-07-25 8:23 ` 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=DBKZP2NMCSHS.N7ZASEZG5HIT@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pve-devel-bounces@lists.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.