From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] fix #6815: ui: resource tree: update tag colors properly
Date: Mon, 13 Oct 2025 06:56:08 +0200 [thread overview]
Message-ID: <176033136621.3558696.13874801387450425277.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251010072802.798062-1-d.csapak@proxmox.com>
On Fri, 10 Oct 2025 09:27:58 +0200, Dominik Csapak wrote:
> In commit:
> e19de81f (ui: resource tree: fix change detection)
> the change detection for resource tree nodes was fixed so that it did
> not update on every refresh anymore.
>
> This now also means that when the ui options are loaded (which contains
> the tag color overrides) we now have to correctly update nodes which
> contains tags, otherwise the standard colors will be shown.
>
> [...]
Applied to master and stable-8, thanks!
[1/1] fix #6815: ui: resource tree: update tag colors properly
commit: 952a4f615731c3de0351c94b83bd97340c7e7798
_______________________________________________
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-10-13 4:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 7:27 [pve-devel] " Dominik Csapak
2025-10-10 7:30 ` Dominik Csapak
2025-10-13 4:56 ` Thomas Lamprecht [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=176033136621.3558696.13874801387450425277.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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.