From: Christian Ebner <c.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@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:07:20 +0200 [thread overview]
Message-ID: <723cddde-088e-4b52-9d10-b5f4c4be5e1e@proxmox.com> (raw)
In-Reply-To: <20260428111822.2471005-1-d.csapak@proxmox.com>
On 4/28/26 1:16 PM, Dominik Csapak wrote:
> having to go into the namespace to move it seems unintuitive, so allow
> it from it's parent too.
>
> Since it touches the same lines, fix the formatting issue detected with
> proxmox-biome.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> 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?
>
> Would appreciate input on what users might expect here...
IMO it would make sense to stay on the same parent and not navigate
away, so a user can subsequently move additional namespaces from that
parent location without much hurdle. I seen not much benefit from moving
to different locations.
next prev parent reply other threads:[~2026-08-31 10:07 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
2026-08-31 10:07 ` Christian Ebner [this message]
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=723cddde-088e-4b52-9d10-b5f4c4be5e1e@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=d.csapak@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 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.