From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: superseded: [PATCH pmg-gui] spam quarantine: add keyboard shortcut for mark-unseen action
Date: Tue, 9 Jun 2026 12:55:35 +0200 [thread overview]
Message-ID: <1b97a5d6-00a4-4b0f-8f6d-2d3d08e7cb07@proxmox.com> (raw)
In-Reply-To: <4829b656-0bbd-4f5a-9c05-f0a6b0de6a68@proxmox.com>
On 6/9/26 12:51 PM, Thomas Lamprecht wrote:
> On 09/06/2026 12:50, Dominik Csapak wrote:
>> if we want to include this, i'd push/send a follow up with adding this to the help of course
>
> Sending a v2 would be IMO the simplest and cleanest approach here IMO.
fair :) so i sent a v2 with it included:
https://lore.proxmox.com/pmg-devel/20260609105510.2027392-1-d.csapak@proxmox.com/T/#u
prev parent reply other threads:[~2026-06-09 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:46 [PATCH pmg-gui] spam quarantine: add keyboard shortcut for mark-unseen action Dominik Csapak
2026-06-09 10:50 ` Dominik Csapak
2026-06-09 10:52 ` Thomas Lamprecht
2026-06-09 10:55 ` Dominik Csapak [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=1b97a5d6-00a4-4b0f-8f6d-2d3d08e7cb07@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=t.lamprecht@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