From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] partially-applied: [PATCH manager 0/4] ui: improve ux for nested pools
Date: Thu, 22 Jan 2026 20:59:05 +0100 [thread overview]
Message-ID: <176911192771.3853907.17285090993935632163.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260122140143.2256222-1-d.csapak@proxmox.com>
On Thu, 22 Jan 2026 14:58:30 +0100, Dominik Csapak wrote:
> by
> * allowing to select a parent pool when creating
> * showing nested pools in the tree as such
>
> patch 1/4 is just a cleanup i noticed during development, and can be
> applied independently
>
> [...]
Applied, thanks!
[1/4] ui: tree: don't show empty grouping nodes as expandable
commit: 04ba61bc6c20f8c223b09f8d3cf0c7319441e33b
[2/4] ui: pool create: allow selecting parent pool via selector
SKIPPED
[3/4] ui: tree: show nested pools in a nested way
commit: a63866dc52b230d7273492639d53abb356b4a345
[4/4] ui: tree: render nested pool names without parent pools
commit: c9d7571baab5e6d13c399a39e90ffe950f6b0189
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-22 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 13:58 [pve-devel] " Dominik Csapak
2026-01-22 13:58 ` [pve-devel] [PATCH manager 1/4] ui: tree: don't show empty grouping nodes as expandable Dominik Csapak
2026-01-22 13:58 ` [pve-devel] [PATCH manager 2/4] ui: pool create: allow selecting parent pool via selector Dominik Csapak
2026-01-22 15:59 ` Thomas Lamprecht
2026-01-23 8:13 ` [pve-devel] superseded: " Dominik Csapak
2026-01-22 13:58 ` [pve-devel] [PATCH manager 3/4] ui: tree: show nested pools in a nested way Dominik Csapak
2026-01-22 13:58 ` [pve-devel] [PATCH manager 4/4] ui: tree: render nested pool names without parent pools Dominik Csapak
2026-01-22 19:59 ` 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=176911192771.3853907.17285090993935632163.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.