From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Herzig <d.herzig@proxmox.com>
Subject: [pve-devel] applied: [PATCH storage v3] dirplugin: fix #3986: check for trailing slashes
Date: Sun, 6 Apr 2025 21:20:12 +0200 [thread overview]
Message-ID: <7ffe5e14-711f-485f-bac9-11284624712f@proxmox.com> (raw)
In-Reply-To: <20241122165725.10378-1-d.herzig@proxmox.com>
Am 22.11.24 um 17:57 schrieb Daniel Herzig:
> Currently, setting up a directory storage with trailing slashes in
> the path results in log messages with double slashes, if this path
> gets expanded by an action like vzdump.
>
> This patch removes those trailing slashes once the directory storage
> class config gets updated.
>
> Signed-off-by: Daniel Herzig <d.herzig@proxmox.com>
> ---
> changes since v2:
> * make use of File::Spec->canonpath() for better readability
>
> v2: https://lore.proxmox.com/pve-devel/20241122131305.59062-1-d.herzig@proxmox.com/
>
> Thanks for the hint, Thomas!
>
> Notes:
>
> Functionality can be tested by adding new directory storage with trailing
> slashes either via the GUI or `pvesm add dir $STORAGENAME --path /some/path/`.
>
> `/new/path/` will show up as `/new/path` in `/etc/pve/storage.cfg`, and trailing
> slashes from earlier defined directory storage paths will be removed.
>
> src/PVE/Storage/DirPlugin.pm | 3 +++
> 1 file changed, 3 insertions(+)
>
>
applied, with commit message/subject slightly adapted, e.g. mentioned
that this is mostly a cosmetic issue and moved the fix # to the front,
thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-06 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 16:57 [pve-devel] " Daniel Herzig
2025-04-06 19:20 ` 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=7ffe5e14-711f-485f-bac9-11284624712f@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.herzig@proxmox.com \
--cc=pve-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal