From: Dominik Csapak <d.csapak@proxmox.com>
To: Jonas Theisen <j.theisen@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [RFC PATCH proxmox-backup] ui: datastore content: allow moving namespace from parent
Date: Mon, 31 Aug 2026 12:06:28 +0200 [thread overview]
Message-ID: <52026382-8959-44a7-b7c0-f4c1d5e0441e@proxmox.com> (raw)
In-Reply-To: <1998f6dd-e34c-408e-840f-96e5b2ec79d2@proxmox.com>
On 8/31/26 11:53 AM, Jonas Theisen wrote:
> On 8/31/26 11:25, Dominik Csapak wrote:
>> ping, any feedback on this?
> On 4/28/26 11:26 Dominik Csapak wrote:
>> sending as RFC because it's not urgent and IMHO it's not clear how we
>> should behave after moving: when inside the namespace it's clear,
>> we change the current view to the new place.
>>
>> But how should we handle it when we move it from the parent?
>> Should we navigate to the new parent? Or should we move inside the
>> new path (as it's currently handled) or should we stay on the same
>> namespace and not navigate away?
> To me it seems most sensible to not move away at all,
> since we also do not navigate to the new path for a VM move.
thanks for the insight, I also think staying in the current
view makes most sense
>
> Fyi the patch in its current version does not apply for me.
yeah, i feared as much. wanted to gather feedback before sending a
new version though
next prev parent reply other threads:[~2026-08-31 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 11:16 [RFC PATCH proxmox-backup] ui: datastore content: allow moving namespace from parent Dominik Csapak
2026-08-31 9:25 ` Dominik Csapak
2026-08-31 9:53 ` Jonas Theisen
2026-08-31 10:06 ` Dominik Csapak [this message]
2026-08-31 10:07 ` Christian Ebner
2026-08-31 11:36 ` superseded: " Dominik Csapak
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=52026382-8959-44a7-b7c0-f4c1d5e0441e@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=j.theisen@proxmox.com \
--cc=pbs-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