From: Dominik Csapak <d.csapak@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>,
Proxmox Datacenter Manager development discussion
<pdm-devel@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager/proxmox-yew-comp v3 0/5] move task description table to yew-comp
Date: Mon, 9 Mar 2026 11:01:13 +0100 [thread overview]
Message-ID: <56bbe853-a24c-400f-8fba-2ea9c4fa8568@proxmox.com> (raw)
In-Reply-To: <DGY5CIVBSMZE.MU4EAC3ETA94@proxmox.com>
On 3/9/26 10:33 AM, Lukas Wagner wrote:
> On Fri Feb 6, 2026 at 1:40 PM CET, Lukas Wagner wrote:
>> On Thu Dec 18, 2025 at 2:28 PM CET, Lukas Wagner wrote:
>>> Changes since v1:
>>> - Break out new task descriptions which snuck in when moving the PVE definitions
>>>
>>> Changes since v2:
>>> - Some smaller code structure fixups (e.g. inlining variables in format!)
>>> - Add missing case in render_datastore_worker_id (thx @ Dominik C)
>>>
>>>
>>> proxmox-yew-comp:
>>>
>>> Lukas Wagner (3):
>>> utils: move task descriptions to a submodule
>>> task descriptions: add PBS task descriptions
>>> task descriptions: add 'create_zone', 'create_vnet' and
>>> 'reloadnetworkall'
>>>
>>> src/utils/mod.rs | 228 +-----------------
>>> src/utils/task_descriptions.rs | 410 +++++++++++++++++++++++++++++++++
>>> 2 files changed, 422 insertions(+), 216 deletions(-)
>>> create mode 100644 src/utils/task_descriptions.rs
>>>
>>>
>>> proxmox-datacenter-manager:
>>>
>>> Lukas Wagner (2):
>>> ui: register task descriptions for some native PDM tasks
>>> ui: use task descriptions from yew-comp for PBS and PVE
>>>
>>> ui/src/lib.rs | 2 +-
>>> ui/src/main.rs | 7 +--
>>> ui/src/tasks.rs | 122 ++++++++----------------------------------------
>>> 3 files changed, 25 insertions(+), 106 deletions(-)
>>>
>>>
>>> Summary over all repositories:
>>> 5 files changed, 447 insertions(+), 322 deletions(-)
>>
>> ping - the PDM patches can be applied now, yew-comp has been bumped.
>> The required changes were included in yew-comp 0.8.1; in PDM we already
>> depend on 0.8.3
>
> ping - would be nice to get these applied (or a quick ack so that I can
> apply them myself) ...
>
>
>
>
>
applied them now, sorry for the delay on that...
prev parent reply other threads:[~2026-03-09 10:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 13:28 Lukas Wagner
2025-12-18 13:28 ` [pdm-devel] [PATCH proxmox-yew-comp v3 1/3] utils: move task descriptions to a submodule Lukas Wagner
2025-12-18 13:56 ` [pdm-devel] applied: " Dominik Csapak
2025-12-18 13:28 ` [pdm-devel] [PATCH proxmox-yew-comp v3 2/3] task descriptions: add PBS task descriptions Lukas Wagner
2025-12-18 13:56 ` [pdm-devel] applied: " Dominik Csapak
2025-12-18 13:28 ` [pdm-devel] [PATCH proxmox-yew-comp v3 3/3] task descriptions: add 'create_zone', 'create_vnet' and 'reloadnetworkall' Lukas Wagner
2025-12-18 13:56 ` [pdm-devel] applied: " Dominik Csapak
2025-12-18 13:28 ` [pdm-devel] [PATCH datacenter-manager v3 1/2] ui: register task descriptions for some native PDM tasks Lukas Wagner
2026-03-09 10:00 ` applied: " Dominik Csapak
2025-12-18 13:28 ` [pdm-devel] [PATCH datacenter-manager v3 2/2] ui: use task descriptions from yew-comp for PBS and PVE Lukas Wagner
2026-03-09 10:00 ` applied: " Dominik Csapak
2025-12-18 13:59 ` [pdm-devel] [PATCH datacenter-manager/proxmox-yew-comp v3 0/5] move task description table to yew-comp Dominik Csapak
2026-02-06 12:40 ` Lukas Wagner
2026-03-09 9:33 ` Lukas Wagner
2026-03-09 10:01 ` 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=56bbe853-a24c-400f-8fba-2ea9c4fa8568@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pdm-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