From: Jonas Theisen <j.theisen@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup] ui: datastore content: allow moving namespace from parent
Date: Mon, 31 Aug 2026 14:05:57 +0200 [thread overview]
Message-ID: <3311b35e-a85e-4db9-9572-aa11cc7f385e@proxmox.com> (raw)
In-Reply-To: <20260831113539.2622191-1-d.csapak@proxmox.com>
On 8/31/26 13:35, Dominik Csapak wrote:
> having to go into the namespace to move it seems unintuitive, so allow
> it from it's parent too.
>
> Only navigate to the new place when we were inside the namespace,
> otherwise we stay at the one we were.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>
> -snip-
Tested the patch by creating and moving Namespaces from the
parent and sub level. Works as expected.
With the patch applied the Root entry of a Namespace also has
a move button and it references the current Namespace.
This is probably not intentional and could cause confusion.
--
Tested-By: Jonas Theisen <j.theisen@proxmox.com>
next prev parent reply other threads:[~2026-08-31 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 11:35 [PATCH proxmox-backup] ui: datastore content: allow moving namespace from parent Dominik Csapak
2026-08-31 12:05 ` Jonas Theisen [this message]
2026-08-31 12:25 ` 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=3311b35e-a85e-4db9-9572-aa11cc7f385e@proxmox.com \
--to=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 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.