From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs/wt/manager] implement tagview
Date: Wed, 23 Aug 2023 10:16:36 +0200 [thread overview]
Message-ID: <b3f69018-6f43-4407-abb3-602ccb09313c@proxmox.com> (raw)
In-Reply-To: <20230802105338.2428817-1-d.csapak@proxmox.com>
On 8/2/23 12:53, Dominik Csapak wrote:
> this adds a 'tagview' to the web ui, organizing guests by their tags
> (for details see the pve-manager patch)
Gave this a quick test on the respective latest master branches. Seems
to work as advertised. Consider this:
Tested-by: Lukas Wagner <l.wagner@proxmox.com>
--
- Lukas
prev parent reply other threads:[~2023-08-23 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 10:53 Dominik Csapak
2023-08-02 10:53 ` [pve-devel] [PATCH docs 1/1] gui: add anchor for tags chapter Dominik Csapak
2023-08-02 10:53 ` [pve-devel] [PATCH widget-toolkit 1/1] css: add some conditions to the tag classes for the tag view Dominik Csapak
2023-08-02 10:53 ` [pve-devel] [PATCH manager 1/1] ui: implement 'Tag View' for the resource tree Dominik Csapak
2023-08-23 8:16 ` 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=b3f69018-6f43-4407-abb3-602ccb09313c@proxmox.com \
--to=l.wagner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox