From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH proxmox-backup] api: create target namespace when moving and it doesn't exist yet
Date: Fri, 24 Apr 2026 21:06:50 +0200 [thread overview]
Message-ID: <177705760883.3360887.11910404636789148584.b4-ty@b4> (raw)
In-Reply-To: <20260424112420.207317-1-h.laimer@proxmox.com>
On Fri, 24 Apr 2026 13:24:20 +0200, Hannes Laimer wrote:
> So the behaviour is the same what a normal `mv` would do. What still
> stays required is the existance of the parent to which the namespace is
> moved.
Applied, thanks!
[1/1] api: create target namespace when moving and it doesn't exist yet
commit: 6c64dc4922b0b541bb01167d50610965ea234717
prev parent reply other threads:[~2026-04-24 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 11:24 Hannes Laimer
2026-04-24 19:06 ` 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=177705760883.3360887.11910404636789148584.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@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